update_event_command · RPG Maker MZ MCP Server MCP

WHAT IT DOES

What update_event_command does on RPG Maker MZ MCP Server

AI agents use update_event_command 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.

WHY IT NEEDS A POLICY

Why update_event_command needs a policy

The tool performs a reversible modification (update) of event data structures. It changes game logic and behaviors but does not irreversibly delete data, execute arbitrary code, or involve financial operations. The severity is medium because misuse could corrupt game logic or create unintended event behaviors, but updates are typically reversible via undo or re-editing.

From the tool's definition Tool description states 'Update an event command at specified index' — this modifies existing event commands within RPG Maker MZ projects by changing their properties or behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_event_command Rate-limited

update_event_command stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_event_command": {
      "limits": [
        {
          "counter": "update_event_command_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RPG Maker MZ MCP Server, so you can run agents against it safely.

FAQ

Questions about update_event_command

What does the update_event_command tool do? +

Update an event command at specified index. 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.

How do I enforce a policy on update_event_command? +

Register the RPG Maker MZ MCP Server MCP server in PolicyLayer and add a rule for update_event_command: 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.

What risk level is update_event_command? +

update_event_command is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_event_command? +

Yes. Add a rate_limit block to the update_event_command 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.

How do I block update_event_command completely? +

Set action: deny in the PolicyLayer policy for update_event_command. 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.

What MCP server provides update_event_command? +

update_event_command 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.