file_reservation_paths
AI agents call file_reservation_paths to retrieve information from MCP Agent Mail without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, classification relies on naming convention and server context. The 'file_reservation_paths' name pattern (noun/data-focused, not action-verb-focused like 'acquire', 'force_release', or 'ensure') and its sibling tools (acquire/force_release suggest explicit write/destructive operations) indicate this is a read/query operation. Lower confidence due to empty description.
From the tool's definition Tool name 'file_reservation_paths' with empty description suggests it queries or lists file reservation information.
Attacks that exploit this kind of access
file_reservation_paths. It is categorised as a Read tool in the MCP Agent Mail MCP Server, which means it retrieves data without modifying state.
Register the MCP Agent Mail MCP server in PolicyLayer and add a rule for file_reservation_paths: 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.
file_reservation_paths is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the file_reservation_paths 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 file_reservation_paths. 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.
file_reservation_paths 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 →