release_file_reservations
AI agents use release_file_reservations to create or update resources in MCP Agent Mail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Agent Mail environment.
Based on the server context (file reservation leases to prevent agents from overwriting each other's work) and the tool name, this tool likely releases file reservations/leases held by agents. Releasing a reservation is a reversible state change (another agent can re-acquire), placing it in the Write category. It is less severe than 'force_release_file_reservation' which implies overriding another agent's lock.
From the tool's definition Tool name: release_file_reservations; description is empty. Sibling tools include 'acquire_build_slot', 'force_release_file_reservation', and 'file_reservation_paths', indicating a file reservation/lease system.
Attacks that exploit this kind of access
release_file_reservations. It is categorised as a Write tool in the MCP Agent Mail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Agent Mail MCP server in PolicyLayer and add a rule for release_file_reservations: 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.
release_file_reservations is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the release_file_reservations 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 release_file_reservations. 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.
release_file_reservations 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 →