Draft a map event
AI agents use create_map_event_draft to create or update resources in RPG Maker MV Content Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RPG Maker MV Content Bridge environment.
This tool creates or stages new map event data within an RPG Maker MV project. It modifies project state by adding content, but the 'draft' pattern means changes are not yet committed to disk—they can be discarded or reviewed before application. This is Write (reversible creation/modification), not Destructive.
From the tool's definition Tool name 'create_map_event_draft' and description 'Draft a map event' indicate content creation. The 'draft' suffix and server description stating 'safely write content' suggest changes are staged but reversible via discard_pending_changes.
Attacks that exploit this kind of access
Draft a map event. It is categorised as a Write tool in the RPG Maker MV Content Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RPG Maker MV Content Bridge MCP server in PolicyLayer and add a rule for create_map_event_draft: 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.
create_map_event_draft 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 create_map_event_draft 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 create_map_event_draft. 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.
create_map_event_draft 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 →