setup_api_key · AdButler MCP: Risk & Policy

WHAT IT DOES

What setup_api_key does on AdButler

AI agents use setup_api_key to create or update resources in AdButler — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.

PARAMETERS

Parameter	Type	Required	Description
`api_key`	string	Yes	The AdButler API key

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why setup_api_key needs a policy

This tool writes a configuration setting (API key) that is stored persistently and enables access to the AdButler platform. It does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial).

From the tool's definition Tool description states "Configure AdButler with an existing API key", which persists a credential to enable API access. The action modifies system configuration (storing authentication material).

Risk signalsHandles credentials or secrets (api_key)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

setup_api_key Rate-limited

setup_api_key stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setup_api_key": {
      "limits": [
        {
          "counter": "setup_api_key_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AdButler, so you can run agents against it safely.

FAQ

Questions about setup_api_key

What does the setup_api_key tool do? +

Configure AdButler with an existing API key. Use this if the user already has an AdButler account and API key. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does setup_api_key accept? +

setup_api_key accepts 1 parameter: api_key. Required: api_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on setup_api_key? +

Register the AdButler MCP server in PolicyLayer and add a rule for setup_api_key: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches AdButler. Nothing to install.

What risk level is setup_api_key? +

setup_api_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit setup_api_key? +

Yes. Add a rate_limit block to the setup_api_key rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block setup_api_key completely? +

Set action: deny in the PolicyLayer policy for setup_api_key. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides setup_api_key? +

setup_api_key is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.