AI agents call find_script_usages to retrieve information from Unity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query across Unity's scene and prefab graph to locate where a script is used. It has no side effects—it does not execute code, modify data, create/delete objects, or affect runtime state. The severity is low because misuse (e.g., excessive queries) would have minimal blast radius and cannot cause data loss or unintended code execution.
From the tool's definition Tool name 'find_script_usages' and description states it 'Find[s] every scene object and prefab that has a specific C# script attached as a component.' This is a search/query operation that retrieves information about script usage without modifying,…
Attacks that exploit this kind of access
Find every scene object and prefab that has a specific C# script attached as a component. It is categorised as a Read tool in the Unity MCP Server, which means it retrieves data without modifying state.
Register the Unity MCP server in PolicyLayer and add a rule for find_script_usages: 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. Nothing to install.
find_script_usages 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 find_script_usages 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 find_script_usages. 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.
find_script_usages is provided by the Unity MCP server (verysleepylemon/unity-mcp). 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 →