get_allowed_paths
AI agents call get_allowed_paths to retrieve information from File Search Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about allowed file paths, which is a read-only operation with no side effects. The empty description lowers confidence slightly, but the naming convention and server context clearly indicate it queries rather than modifies state. Risk is low given that path enumeration alone does not expose sensitive data without subsequent read operations.
From the tool's definition The tool name 'get_allowed_paths' and server description indicate file system inspection capabilities. The server is explicitly described as enabling 'file system search and inspection, including directory listing' with no mention of modification or deletion.
Attacks that exploit this kind of access
get_allowed_paths. It is categorised as a Read tool in the File Search Tool MCP Server, which means it retrieves data without modifying state.
Register the File Search Tool MCP server in PolicyLayer and add a rule for get_allowed_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 File Search Tool. Nothing to install.
get_allowed_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 get_allowed_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 get_allowed_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.
get_allowed_paths is provided by the File Search Tool MCP server (rjtpp/mcp-server-file-search-tool). 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 →