AI agents call search_within_files to retrieve information from Filesystem MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations retrieve and filter data without side effects. No modification, deletion, or execution capabilities are implied. This belongs in the Read category with low severity, as it only locates and returns matching content within files.
From the tool's definition Tool name 'search_within_files' indicates a read operation that queries file contents without modification.
Documented attack patterns abuse exactly the kind of access search_within_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Filesystem MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_within_files:
{
"version": "1",
"default": "deny",
"tools": {
"search_within_files": {}
}
}search_within_files is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_within_files. It is categorised as a Read tool in the Filesystem MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Filesystem MCP Server MCP server in PolicyLayer and add a rule for search_within_files: 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 Filesystem MCP Server. Nothing to install.
search_within_files 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 search_within_files 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 search_within_files. 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.
search_within_files is provided by the Filesystem MCP Server MCP server (mark3labs/mcp-filesystem-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Filesystem MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Filesystem MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.