Get basic information about the RPG Maker MZ project from System.json
AI agents call get_project_info 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.
This tool retrieves metadata about the project configuration from a static JSON file. It performs a query operation with no capability to modify data, execute code, or trigger external actions. The blast radius of misuse is minimal—an AI agent could only read harmless project metadata like version numbers, title, or settings.
From the tool's definition Tool name is 'get_project_info' and description states 'Get basic information...from System.json', indicating a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get basic information about the RPG Maker MZ project from System.json. 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 get_project_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 RPG Maker MZ MCP Server. Nothing to install.
get_project_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_project_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_project_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_project_info 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 →