Get physics body state (velocity, angular velocity, contacts) for a node in the running game.
AI agents call get_physics_state to retrieve information from Godot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves physics information from a running game. It performs a read-only operation with no side effects: it does not create, modify, delete, or execute arbitrary code. The data returned (velocity, angular velocity, contacts) is informational only.
From the tool's definition Tool description states 'Get physics body state (velocity, angular velocity, contacts)' — uses the verb 'Get' and retrieves runtime physics data without modifying or triggering any game state changes.
Attacks that exploit this kind of access
Get physics body state (velocity, angular velocity, contacts) for a node in the running game. It is categorised as a Read tool in the Godot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for get_physics_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 Godot MCP Server. Nothing to install.
get_physics_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_physics_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_physics_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_physics_state is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). 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 →