List entity counts
AI agents call list_project_data to retrieve information from RPG Maker MV Content Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—listing counts of entities in an RPG Maker MV project. It has no side effects, does not modify or delete data, and does not execute code or trigger external operations. The low severity reflects minimal blast radius: misuse would only expose non-sensitive summary statistics about the project structure.
From the tool's definition Tool name 'list_project_data' and description 'List entity counts' indicate a query operation that retrieves aggregate information about existing project entities without modifying, deleting, or executing code.
Attacks that exploit this kind of access
List entity counts. It is categorised as a Read tool in the RPG Maker MV Content Bridge MCP Server, which means it retrieves data without modifying state.
Register the RPG Maker MV Content Bridge MCP server in PolicyLayer and add a rule for list_project_data: 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 MV Content Bridge. Nothing to install.
list_project_data 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 list_project_data 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 list_project_data. 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.
list_project_data is provided by the RPG Maker MV Content Bridge MCP server (zdoss/herolink). 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 →