Find all GameObjects in the scene that have a specific component type. Returns their paths and instance IDs.
AI agents call unity_search_by_component to retrieve information from Unity MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries scene data and returns results. It has no side effects—it neither modifies game objects, executes scripts, deletes assets, nor triggers external operations. The search scope is limited to existing scene components, making blast radius minimal even if misused by an AI agent.
From the tool's definition Tool performs a search/query operation ('Find all GameObjects in the scene that have a specific component type') and returns data ('paths and instance IDs') with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access unity_search_by_component gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for unity_search_by_component:
{
"version": "1",
"default": "deny",
"tools": {
"unity_search_by_component": {}
}
}unity_search_by_component 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.
Find all GameObjects in the scene that have a specific component type. Returns their paths and instance IDs. It is categorised as a Read tool in the Unity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_search_by_component: 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 Server. Nothing to install.
unity_search_by_component 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 unity_search_by_component 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 unity_search_by_component. 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.
unity_search_by_component is provided by the Unity MCP Server MCP server (anklebreaker-studio/unity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 324 Unity MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
324 Unity MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.