Search note fields/meta
AI agents call search_notes 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.
This tool performs a read-only search across note fields and metadata in the RPG Maker MV project. It retrieves information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an AI agent could only retrieve unintended data, not corrupt or delete the project or execute arbitrary code.
From the tool's definition Tool name 'search_notes' and description 'Search note fields/meta' indicate a query operation that retrieves data without modification. The verb 'search' is explicitly listed in the Read category definition as a non-side-effect operation.
Attacks that exploit this kind of access
Search note fields/meta. 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_notes: 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_notes 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_notes 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_notes. 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_notes 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 →