Permanently delete a connection and all its cached schema + semantic metadata.
AI agents call delete_connection to permanently remove resources in Querywise — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation ('Permanently delete') affecting both the connection configuration and associated cached metadata. While not as immediately severe as deleting production data, the permanent removal of schema and semantic metadata (glossary terms, metrics, sample queries, dictionary entries tied to that connection) represents a destructive action that cannot be undone.
From the tool's definition Tool name 'delete_connection' combined with description 'Permanently delete a connection and all its cached schema + semantic metadata' explicitly indicates irreversible deletion of data and configurations.
Attacks that exploit this kind of access
Permanently delete a connection and all its cached schema + semantic metadata. It is categorised as a Destructive tool in the Querywise MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Querywise 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 Querywise. 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 Querywise MCP server (kosminus/querywise-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 →