delete_event_command

Delete an event command at specified index

Server RPG Maker MZ MCP Server rein1225/rpgmakermz_mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_event_command does on RPG Maker MZ MCP Server

AI agents call delete_event_command to permanently remove resources in RPG Maker MZ MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_event_command needs a policy

This tool permanently removes event commands from RPG Maker MZ projects without undo capability. While the blast radius is limited to a single game project (not system-wide or financial), deletion of event commands is an irreversible operation that destroys game logic and content. This fits the Destructive category more severely than Execute, since the action cannot be undone and constitutes permanent data loss.

From the tool's definition Tool name contains 'delete' and description states it will 'Delete an event command at specified index' - this is irreversible removal of game content.

Questions about delete_event_command

What does the delete_event_command tool do? +

Delete an event command at specified index. It is categorised as a Destructive tool in the RPG Maker MZ MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_event_command? +

Register the RPG Maker MZ MCP Server MCP server in PolicyLayer and add a rule for delete_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 delete_event_command? +

delete_event_command is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_event_command? +

Yes. Add a rate_limit block to the delete_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 delete_event_command completely? +

Set action: deny in the PolicyLayer policy for delete_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 delete_event_command? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.