Validate project references
AI agents call validate_project_refs 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 validation—an inspection and verification activity that does not create, modify, delete, or execute arbitrary code. It is consistent with the 'Read' category (retrieves or queries data; no side effects). Severity is low because validation failures are informational and cannot cause data loss or harmful execution.
From the tool's definition Tool name 'validate_project_refs' and description 'Validate project references' indicate a checking/validation operation with no modification or deletion. Validation is a read-only analysis operation that checks integrity without side effects.
Attacks that exploit this kind of access
Validate project references. 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 validate_project_refs: 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.
validate_project_refs 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 validate_project_refs 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 validate_project_refs. 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.
validate_project_refs 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 →