Search event text
AI agents call search_events to retrieve information from RPG Maker MV Content Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search operation on event text within an RPG Maker MV project. Searching and querying data are Read category operations that retrieve information without modifying, deleting, or executing anything. The low severity reflects that misuse would only expose existing project data, not cause harm or state changes.
From the tool's definition Tool name is 'search_events' and description states 'Search event text', which is a query operation with no side effects.
Attacks that exploit this kind of access
Search event text. It is categorised as a Read tool in the RPG Maker MV Content Bridge MCP Server, which means it retrieves data without modifying state.
Register the RPG Maker MV Content Bridge MCP server in PolicyLayer and add a rule for search_events: 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.
search_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_events 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 search_events. 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.
search_events 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 →