Draft a common event
AI agents use create_common_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 (drafts) new game content in an RPG Maker MV project. It is a Write operation because it creates new data structures. Severity is medium rather than low because a malicious agent could create numerous invalid or disruptive events that clutter the project, though the impact is mitigated by the draft-based workflow (changes are staged, not immediately applied).
From the tool's definition Tool name 'create_common_event_draft' and description 'Draft a common event' indicate creation of new content.
Attacks that exploit this kind of access
Draft a common 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_common_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_common_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_common_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_common_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_common_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 →