AI agents call describe_adbutler_api to retrieve information from AdButler without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Endpoint path with `{placeholder}` syntax for path params, e.g. "/campaigns/{id}". Must match the path returned by search_adbutler_api exactly. |
method | string | Yes | HTTP method, e.g. "GET", "POST", "PUT", "DELETE". |
Parameters from the server's own tool schema.
The tool retrieves schema documentation for an API endpoint. It performs no side effects, creates no data, executes no commands, and deletes nothing. It is purely informational, similar to fetching API documentation. The severity is low because misuse would only result in an AI agent gaining information about available operations, not performing harmful actions directly.
From the tool's definition Tool name 'describe_adbutler_api' and description indicate it 'Get[s] the full schema (parameters, request body shape, response shape)' with no modification of data. This is a query/introspection operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Get the full schema (parameters, request body shape, response shape) for one AdButler API endpoint. Use after search_adbutler_api to understand exactly what to send when you call it. It is categorised as a Read tool in the AdButler MCP Server, which means it retrieves data without modifying state.
describe_adbutler_api accepts 2 parameters: path, method. 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 describe_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.
describe_adbutler_api is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the describe_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 describe_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.
describe_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 →