Delete a specific execution record
AI agents call alfred_delete_execution 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 permanently removes execution records from the system without the ability to undo the operation. While the blast radius is not as critical as deleting workflows or API keys (which would affect ongoing operations), deletion of audit/execution history is destructive and could obscure activity logs.
From the tool's definition Tool name is 'alfred_delete_execution' and description states 'Delete a specific execution record'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a specific execution record. 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_execution: 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_execution 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_execution 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_execution. 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_execution 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 →