force_release_file_reservation
AI agents call force_release_file_reservation to permanently remove resources in MCP Agent Mail — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible action (force-release) that breaks coordination guarantees. While the description is empty, the name combined with server context reveals capability to destroy the integrity of multi-agent file protection. The blast radius is high: misuse could cause unintended file overwrites, lost work, or data corruption in multi-agent workflows.
From the tool's definition Tool name 'force_release_file_reservation' indicates forceful, irreversible release of file reservations that other agents rely on.
Attacks that exploit this kind of access
force_release_file_reservation. It is categorised as a Destructive tool in the MCP Agent Mail MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Agent Mail MCP server in PolicyLayer and add a rule for force_release_file_reservation: 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 MCP Agent Mail. Nothing to install.
force_release_file_reservation 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 force_release_file_reservation 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 force_release_file_reservation. 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.
force_release_file_reservation is provided by the MCP Agent Mail MCP server (omelchmichael/mcp_agent_mail). 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 →