Retrieve information about the current scene in Unity Editor with configurable detail level
AI agents call get_current_scene_info 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.
This tool queries and returns data about the current Unity scene state. It has no side effects—it does not modify scene data, execute code, delete assets, or perform financial operations. It is a pure information retrieval operation, analogous to a 'get' or 'fetch' operation. The configurable detail level is a parameter for filtering output, not for performing different types of actions.
From the tool's definition The tool name is 'get_current_scene_info' and the description states it will 'Retrieve information about the current scene in Unity Editor'.
Documented attack patterns abuse exactly the kind of access get_current_scene_info 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 get_current_scene_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_scene_info": {}
}
}get_current_scene_info 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.
Retrieve information about the current scene in Unity Editor with configurable detail level. 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 get_current_scene_info: 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.
get_current_scene_info 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 get_current_scene_info 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 get_current_scene_info. 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.
get_current_scene_info 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.