AI agents call romm_saves 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 only retrieves and lists save files, filtered by ROM or platform. It performs no modifications, deletions, or executions. Pure read operation with minimal blast radius.
From the tool's definition "List save files. Filter by ROM or platform."
Attacks that exploit this kind of access
List save files. Filter by ROM or platform. 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_saves: 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_saves 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_saves 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_saves. 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_saves 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 →