Delete a connection by ID
AI agents call alfred_delete_connection to permanently remove resources in Alfred MCP Server — 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 on a connection object. Deletion of connections is a destructive action that cannot be undone and may break dependent workflows or integrations. While not a direct data breach or financial impact, the inability to reverse this action and its potential to disrupt operational workflows places it in the Destructive category with high severity.
From the tool's definition Tool name contains 'delete' and description states 'Delete a connection by ID'. Connections are configuration objects that typically cannot be easily recovered once removed.
Attacks that exploit this kind of access
Delete a connection by ID. It is categorised as a Destructive tool in the Alfred MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Alfred MCP Server MCP server in PolicyLayer and add a rule for alfred_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 Alfred MCP Server. Nothing to install.
alfred_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 alfred_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 alfred_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.
alfred_delete_connection is provided by the Alfred MCP Server MCP server (lumberjack-so/alfred-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 →