List pending changes
AI agents call list_pending_changes 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 queries the state of pending changes in the RPG Maker MV project. It has no side effects—it simply retrieves and displays information. No data is created, modified, executed, deleted, or committed. The read-only nature and the absence of any mutating operations place it firmly in the Read category with low severity.
From the tool's definition Tool name is 'list_pending_changes' with description 'List pending changes'. The verb 'list' is a read operation that retrieves and displays information about pending changes without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
List pending changes. 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_pending_changes: 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_pending_changes 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_pending_changes 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_pending_changes. 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_pending_changes 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 →