Recursively search for files and directories matching a pattern in the Unity project.
AI agents call search_files to retrieve information from Unity MCP Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The search_files tool retrieves and queries file system information based on pattern matching. It has no side effects—it does not create, modify, delete, or execute anything. This is a classic read operation analogous to grep or find commands used for discovery. The low severity reflects minimal blast radius: worst case, an agent gains visibility into project structure, which is informational only.
From the tool's definition Tool performs recursive search for files and directories matching a pattern; described as a search operation with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access search_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for search_files:
{
"version": "1",
"default": "deny",
"tools": {
"search_files": {}
}
}search_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.
Recursively search for files and directories matching a pattern in the Unity project. It is categorised as a Read tool in the Unity MCP Integration MCP Server, which means it retrieves data without modifying state.
Register the Unity MCP Integration MCP server in PolicyLayer and add a rule for search_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 Unity MCP Integration. Nothing to install.
search_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_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_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_files is provided by the Unity MCP Integration MCP server (quazaai/unitymcpintegration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Unity MCP Integration tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Unity MCP Integration tools catalogued and risk-classified — across an index of 42,500+ MCP servers.