MCP, API and webhooks

Access, publish limits and what gets filtered

The three levels of access, how the publish limit works, and why your assistant sees fewer tools than exist.

The three levels of access

AccessWhat it allows
ReadRead your Koast data.
WriteChange your Koast data. Drafts, settings, live edits.
PublishPush campaigns live to the ad platform.

They stack. A connection with Read and Write can build a whole campaign and still cannot put it live.

The publish limit

Publish is the only access that spends money, so it carries its own cap. The publish limit is the most one connection may ever put live, in total, across its whole life. It is not a daily budget and it is separate from your ad account budgets.

An API key can be unlimited instead. Turn on Unlimited next to the amount and the key can publish any amount, with no check against a limit. Koast still adds up what the key puts live, and the key's row shows the total. A key has an amount or Unlimited, never both: picking one clears the other. The consent screen of an app you connect by signing in asks for an amount and has no Unlimited choice.

With neither, publishing is refused. The publishing tools don't appear at all until you set an amount or turn on Unlimited, so an assistant can draft an entire launch and still have no way to push it. A key that has neither, including one made before Unlimited existed, stays that way until you change it.

Why your assistant sees fewer tools than exist

The list is filtered on every request, by four things:

  1. The access you granted. Read only hides every write and publish tool.
  2. Your role on the team. A connection you signed in can never do more than you can. An API key acts as an organization admin, limited to the access and brands set on the key.
  3. Your plan. Tools your plan doesn't include are not offered.
  4. The active brand's ad provider. Meta and Koast ad accounts support different things.

A read only connection sees 33 tools. Read, Write and Publish on a Meta brand sees 71.

Filtering happens in the server, not in the prompt

The server refuses a call for a tool that isn't on the list, and names the access that would have carried it. That boundary doesn't depend on the assistant behaving well.

Revoking

Revoke a key or an authorized app from API & Webhooks in Settings. It takes effect on the connection's next request, not at the end of its session. Only the organization owner and admins can revoke API keys.

On this page