AI agents call romm_search to retrieve information from Mcp Romm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries ROM data by name without any side effects or modifications. It is a simple search/lookup operation that only returns matching results from the library, fitting the Read category definition.
From the tool's definition Tool name includes 'search' and description states 'Search ROMs by name across the library' with no mention of modification, deletion, or execution.
Attacks that exploit this kind of access
Search ROMs by name across the library. It is categorised as a Read tool in the Mcp Romm MCP Server, which means it retrieves data without modifying state.
Register the Mcp Romm MCP server in PolicyLayer and add a rule for romm_search: 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 Mcp Romm. Nothing to install.
romm_search 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 romm_search 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 romm_search. 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.
romm_search is provided by the Mcp Romm MCP server (lodordev/mcp-romm). 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 →