Delete a connection from Polytomic.
AI agents call delete_connection to permanently remove resources in Polytomic MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a connection configuration from the Polytomic platform. Once deleted, the connection cannot be recovered without recreating it from scratch. In a Reverse ETL/ELT context, deleting a connection disrupts data pipelines and integration workflows, making it a destructive action with potential operational impact.
From the tool's definition Tool name 'delete_connection' with description 'Delete a connection from Polytomic.' The verb 'delete' indicates irreversible removal of data/configuration.
Attacks that exploit this kind of access
Delete a connection from Polytomic. It is categorised as a Destructive tool in the Polytomic MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Polytomic MCP Server MCP server in PolicyLayer and add a rule for delete_connection: 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 Polytomic MCP Server. Nothing to install.
delete_connection 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_connection 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_connection. 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_connection is provided by the Polytomic MCP Server MCP server (therevenueengineer/polytomic-mcp). 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 →