delete_integration

THE RISK

Critical Risk

Why delete_integration needs a policy

This tool performs deletion of integration configurations, which cannot be undone. While the blast radius is narrower than system-wide destruction (limited to a single integration rather than all data), deletion is inherently irreversible and would require manual reconfiguration to restore. This qualifies as Destructive rather than Write (which is reversible) or Execute (which depends on arguments for side effects).

From the tool's definition Tool name 'delete_integration' with description 'Delete an integration configuration.' - the verb 'Delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_integration gives an agent:

POLICY

How to control delete_integration

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Coroot, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_integration:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_integration"
  ]
}

delete_integration disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register MCP Server for Coroot — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Server for Coroot tools

Destructive delete_api_key Delete an API key. Destructive delete_application_category Delete an application category. Destructive delete_custom_cloud_pricing Delete custom cloud pricing configuration. Destructive delete_dashboard Delete a custom dashboard. Destructive delete_project Delete a project and all associated data. Execute test_integration Test an integration configuration. Write configure_integration configure_integration Write configure_logs configure_logs

All 61 MCP Server for Coroot tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MCP Server for Coroot → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_integration

What does the delete_integration tool do? +

Delete an integration configuration. It is categorised as a Destructive tool in the MCP Server for Coroot 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_integration? +

Register the MCP Server for Coroot MCP server in PolicyLayer and add a rule for delete_integration: 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 MCP Server for Coroot. Nothing to install.

What risk level is delete_integration? +

delete_integration 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_integration? +

Yes. Add a rate_limit block to the delete_integration 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_integration completely? +

Set action: deny in the PolicyLayer policy for delete_integration. 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_integration? +

delete_integration is provided by the MCP Server for Coroot MCP server (jamesbrink/mcp-coroot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Server for Coroot tool call.

Start from MCP Server for Coroot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →