Inspect game variables and switches via Puppeteer. Requires game running with --remote-debugging-port.
AI agents call inspect_game_state to retrieve information from RPG Maker MZ MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves game state information (variables and switches) for inspection purposes. There are no side effects, data modifications, or destructive actions. This is purely observational and diagnostic in nature, fitting the 'Read' category which covers retrieval and queries without side effects. Severity is low because inspecting read-only game state poses minimal risk to game integrity or external systems.
From the tool's definition Tool name 'inspect_game_state' and description 'Inspect game variables and switches' indicate retrieval and querying of runtime state without modification. Puppeteer-based inspection is a passive read operation.
Attacks that exploit this kind of access
Inspect game variables and switches via Puppeteer. Requires game running with --remote-debugging-port. It is categorised as a Read tool in the RPG Maker MZ MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RPG Maker MZ MCP Server MCP server in PolicyLayer and add a rule for inspect_game_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 RPG Maker MZ MCP Server. Nothing to install.
inspect_game_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 inspect_game_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 inspect_game_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.
inspect_game_state is provided by the RPG Maker MZ MCP Server MCP server (rein1225/rpgmakermz_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 →