delete_report_run
A destructive tool on the API-Central MCP server.
This record as markdown: /tools/secure-ssid-centralmcp/delete-report-run.md
What delete_report_run does on API-Central
AI agents call delete_report_run to permanently remove resources in API-Central, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_report_run is rated Critical
The tool name 'delete_report_run' unambiguously indicates permanent deletion of data. Although the description is empty, the naming convention alone is strong evidence of destructive capability. In a network operations context, report runs may contain historical audit trails, compliance records, or operational analytics that cannot be recovered once deleted.
From the tool's definition Tool name is 'delete_report_run' which explicitly indicates deletion of a report run resource. The verb 'delete' is irreversible and matches the destructive category definition.
Attacks that exploit this kind of access
The rule that runs delete_report_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_report_run, this is the rule to start with:
delete_report_run 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 API-Central, apply this rule, and every delete_report_run call is checked against it from then on.
Questions about delete_report_run
delete_report_run is a destructive tool on the API-Central MCP server. It is categorised as a Destructive tool in the API-Central MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the API-Central MCP server in PolicyLayer and add a rule for delete_report_run: 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 API-Central. Nothing to install.
delete_report_run 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_report_run 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_report_run. 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_report_run is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API-Central, and thousands of servers like it.
Across the catalogue