AI agents call search_functions to retrieve information from MCP File Edit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to search or query function definitions within code, which is a read-only operation. No data modification, deletion, or execution capabilities are evident. Confidence is slightly reduced due to empty description, but sibling tools like 'get_function_at_line' and 'get_code_structure' confirm this server performs static analysis and inspection tasks rather than modification or execution.
From the tool's definition Tool name 'search_functions' combined with server's stated purpose of 'reading, searching' and code analysis. No description provided, but naming and context indicate query/retrieval operation without side effects.
Documented attack patterns abuse exactly the kind of access search_functions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP File Edit, and nothing reaches the server without passing your rules. This is the rule we recommend for search_functions:
{
"version": "1",
"default": "deny",
"tools": {
"search_functions": {}
}
}search_functions 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_functions. It is categorised as a Read tool in the MCP File Edit MCP Server, which means it retrieves data without modifying state.
Register the MCP File Edit MCP server in PolicyLayer and add a rule for search_functions: 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 File Edit. Nothing to install.
search_functions 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_functions 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_functions. 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_functions is provided by the MCP File Edit MCP server (patrickomatik/mcp-file-edit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP File Edit, 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.
32 MCP File Edit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.