Skip to content

ConsentAlly works with AI assistants. A merchant can have their assistant set up, sign in to or check their ConsentAlly account from the chat: the assistant needs only the merchant's email address, and the merchant approves it on one ConsentAlly page with a code. Nothing is created or connected before that approval. How it works: https://consentally.com/auth.md

Docs pages

What an agent can and cannot do

An AI assistant connected to ConsentAlly works only through named tools, the same at the MCP server and at the HTTP API. Each tool either reads or changes the account, and the changes visitors would see ask the person first; none deletes, unpublishes or pays. The table below is generated from ConsentAlly's tool registry, so it lists every tool there is and no other.

The tools

Every tool an assistant can call
ToolWhat it is forReads or changesAsks the person first
next_stepsWhat to do nextReadsNo
add_storeAdd a websiteChangesNo
set_jurisdictionsSet where the business sellsChangesNo
get_configRead the banner settingsReadsNo
update_bannerChange the banner draftChangesNo
publishPublish the bannerChangesAlways
install_snippetGet the install tagReadsNo
install_statusCheck the installReadsNo
rollbackGo back to an earlier versionChangesAlways
list_scriptsList the website's scriptsReadsNo
classify_scriptSet a script's categoryChangesWhen the change lets a script run before the visitor chooses
consent_statsConsent figuresReadsNo
lookup_consentLook up a consent recordReadsNo
plan_optionsPlans and pricesReadsNo
billing_linkLink to change the planReadsNo
An assistant starts with next_steps: it lists the person's websites, where each one's setup stands and the one thing to do now, and every answer after it carries its own next.

What decides what a connection may do

  • What the person granted. Read only, or read and change, which only an organisation admin can grant. A read-only connection is refused every tool that changes something, before the website is looked at.
  • Which websites. All of the organisation's websites, or the one the person chose. Another account's website answers exactly as one that does not exist.
  • The plan. Each call is checked against the organisation's plan as the dashboard checks the same action; a refusal names the first plan that allows it, and billing_link gives the person the link to change it themselves.
  • Rate limits. Adding websites, consent figures and record lookups are limited per connection or per organisation, and a refusal says when to try again.

What an agent can never do

  • Delete or unpublish anything: there is no tool that removes a website, a banner version, a consent record or an account, or takes a banner down.
  • Pay, start a trial, choose a plan or accept terms for the person.
  • Approve its own connection, or connect itself to an account without the person approving on ConsentAlly's page.
  • Read another organisation's data, or a website the person did not grant.

How changes are confirmed and undone is in Confirmation and undo. What ConsentAlly itself does not do is on Limitations.