Delete a Nango integration.
AI agents call delete_integration to permanently remove resources in Nango — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes an integration, which cannot be undone. Deletion is the core definition of the Destructive category. The severity is high because deleting an integration could disable critical API connections and dependent systems, though it may not directly expose financial data or affect multiple organizations simultaneously. High confidence based on explicit 'delete' language.
From the tool's definition Tool name is 'delete_integration' and description states 'Delete a Nango integration.' The verb 'delete' combined with the description explicitly indicates permanent removal of data.
Attacks that exploit this kind of access
Delete a Nango integration. It is categorised as a Destructive tool in the Nango MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nango 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 Nango. Nothing to install.
delete_integration 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_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.
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.
delete_integration is provided by the Nango MCP server (levsky22/nango-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 →