New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_report_run

A destructive tool on the API-Central MCP server.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_report_run

What does the delete_report_run tool do? +

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.

How do I enforce a policy on delete_report_run? +

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.

What risk level is delete_report_run? +

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.

Can I rate-limit delete_report_run? +

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.

How do I block delete_report_run completely? +

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.

What MCP server provides delete_report_run? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of API-Central's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.