This record as markdown: /tools/adbutler/delete-custom-report.md
What delete_custom_report does on AdButler
AI agents call delete_custom_report to permanently remove resources in AdButler, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Report configuration ID |
Parameters from the server's own tool schema.
Why delete_custom_report is rated Critical
Deleting a report configuration is a destructive action that cannot be undone. Once deleted, the configuration is permanently lost unless restored from backups. This fits the Destructive category (irreversibly deletes data) with high severity because an AI agent misusing this tool could destroy important reporting infrastructure that may be relied upon for business analytics and decision-making.
From the tool's definition Tool name contains 'delete' and description states 'Delete a report configuration', indicating irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_custom_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_custom_report, this is the rule to start with:
delete_custom_report is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every delete_custom_report call is checked against it from then on.
Questions about delete_custom_report
Delete a report configuration. It is categorised as a Destructive tool in the AdButler MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_custom_report accepts 1 parameter: id. Required: id. 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 delete_custom_report: 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.
delete_custom_report is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_custom_report 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 delete_custom_report. 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.
delete_custom_report 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.
More on AdButler, and thousands of servers like it.
Across the catalogue