AI agents call get_state to retrieve information from Unity-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the description is empty, the tool name 'get_state' and its contextual placement alongside other read-only 'get_*' tools strongly indicate this retrieves data about the game environment's current state without side effects. No mention of mutation, deletion, code execution, or financial operations.
From the tool's definition Tool name 'get_state' suggests a query operation that retrieves state information without modification. The pattern matches sibling tools like 'get_log_by_name' and 'get_logs' which are clearly Read operations.
Documented attack patterns abuse exactly the kind of access get_state gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_state": {}
}
}get_state 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.
get_state. It is categorised as a Read tool in the Unity-MCP MCP Server, which means it retrieves data without modifying state.
Register the Unity- MCP server in PolicyLayer and add a rule for get_state: 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. Nothing to install.
get_state 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_state 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_state. 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_state is provided by the Unity- MCP server (tsavo/unity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Unity-MCP, 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.
7 Unity-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.