Add a break loop command to an event
AI agents use add_break_loop to create or update resources in RPG Maker MZ MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RPG Maker MZ MCP Server environment.
This tool creates or modifies event command sequences within RPG Maker MZ projects. While it changes game behavior, the modification is reversible (commands can be edited or removed), and it doesn't delete data or execute arbitrary code. It's a Write operation because it adds/modifies game event data structures.
From the tool's definition add_break_loop adds a break loop command to an event, which modifies event logic in RPG Maker MZ projects. The verb 'add' and context of event automation indicates creation/modification of game event structures.
Attacks that exploit this kind of access
Add a break loop command to an event. It is categorised as a Write tool in the RPG Maker MZ MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RPG Maker MZ MCP Server MCP server in PolicyLayer and add a rule for add_break_loop: 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.
add_break_loop is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_break_loop 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 add_break_loop. 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.
add_break_loop 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 →