AI agents use romm_set_status 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.
The tool appears to update/change a status property on a resource (likely a game or save state in a ROM management system). This is reversible state modification (Write category), not destructive deletion. Without the description, confidence is moderate, but the naming convention and context of sibling tools strongly suggest it modifies rather than deletes data.
From the tool's definition Tool name 'romm_set_status' indicates modification of a status field. Description is empty, but sibling tools like 'romm_add_note', 'romm_add_to_collection', 'romm_favorite' are clearly Write operations, and 'romm_set_status' follows the same pattern of state…
Attacks that exploit this kind of access
romm_set_status. 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_set_status: 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_set_status 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_set_status 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_set_status. 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_set_status 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 →