Call any AdButler API endpoint directly. Use this only when no specific tool wraps the endpoint you need. The session's configured API key is used automatically — do NOT pass an api_key argument. Substitute path placeholders via path_params: e.g. path="/campaigns/{id}", path_params={ "id": 123 } ...
AI agents invoke call_adbutler_api to trigger actions in AdButler. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | — | JSON request body (for POST/PUT/PATCH). |
path | string | Yes | Endpoint path with `{placeholder}` syntax for path params, exactly as returned by search_adbutler_api (e.g. "/campaigns/{id}"). |
method | string | Yes | HTTP method, e.g. "GET", "POST", "PUT", "DELETE". |
path_params | object | — | Map of path placeholder names to values, e.g. { "id": 123 }. |
query_params | object | — | Query string parameters appended to the URL. |
Parameters from the server's own tool schema.
This tool can call ANY AdButler API endpoint, including destructive operations (delete, archive, purge), financial operations (campaign billing, contracts), and writes. Since it spans all categories, the most severe applicable category is Execute (it could trigger Destructive or Financial operations depending on arguments).
From the tool's definition 'Call any AdButler API endpoint directly' — arbitrary endpoint invocation with any HTTP method, not limited to reads or writes
Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (body)
Attacks that exploit this kind of access
Call any AdButler API endpoint directly. Use this only when no specific tool wraps the endpoint you need. The session's configured API key is used automatically — do NOT pass an api_key argument. Substitute path placeholders via path_params: e.g. path="/campaigns/{id}", path_params={ "id": 123 } → /campaigns/123. It is categorised as a Execute tool in the AdButler MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
call_adbutler_api accepts 5 parameters: body, path, method, path_params, query_params. Required: path, method. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for call_adbutler_api: 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.
call_adbutler_api is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the call_adbutler_api 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.
Set action: deny in the PolicyLayer policy for call_adbutler_api. 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.
call_adbutler_api 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →