AI agents use romm_favorite to create or update resources in Mcp Romm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Romm environment.
This tool modifies a user's favorites list by adding or removing entries. It is a reversible write operation (toggling favorite status) with minimal blast radius — no data is deleted, no code is executed, and no financial transactions occur.
From the tool's definition Add or remove a ROM from your Favorites
Attacks that exploit this kind of access
Add or remove a ROM from your Favorites. It is categorised as a Write tool in the Mcp Romm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Romm MCP server in PolicyLayer and add a rule for romm_favorite: 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_favorite is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the romm_favorite 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_favorite. 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_favorite 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 →