AI agents call romm_user_profile 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 and queries user profile data and ROM status information without creating, modifying, or deleting any data. It is a standard read operation with no side effects or blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Browse ROMs by user status' — browse indicates read-only retrieval of existing data (favorites, now playing, backlogged, completed status). No modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Browse ROMs by user status — favorites, now playing, backlogged, completed. 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_user_profile: 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_user_profile 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_user_profile 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_user_profile. 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_user_profile 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 →