Destroy a connection — stops the source subscriber, cleans up the stream buffer.
AI agents call destroy_connection to permanently remove resources in LiveTap — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The word 'destroy' combined with stopping a subscriber and cleaning up buffers indicates an irreversible action that terminates an active connection and discards associated state. While not data deletion in the traditional sense, destroying a live connection severs monitoring/alerting capability and cannot be undone without manual reconnection setup.
From the tool's definition Tool name 'destroy_connection' and description 'Destroy a connection — stops the source subscriber, cleans up the stream buffer.' explicitly use 'Destroy' and indicate permanent cessation of a live data connection with cleanup operations that cannot be easily…
Documented attack patterns abuse exactly the kind of access destroy_connection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LiveTap, and nothing reaches the server without passing your rules. This is the rule we recommend for destroy_connection:
{
"version": "1",
"default": "deny",
"hide": [
"destroy_connection"
]
}destroy_connection disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Destroy a connection — stops the source subscriber, cleans up the stream buffer. It is categorised as a Destructive tool in the LiveTap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LiveTap MCP server in PolicyLayer and add a rule for destroy_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 LiveTap. Nothing to install.
destroy_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 destroy_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 destroy_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.
destroy_connection is provided by the LiveTap MCP server (livetap/livetap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LiveTap, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 LiveTap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.