AI agents use machines_register to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
This tool creates or records a new machine configuration in the registry, making it a Write action. The severity is medium because registering machines could enable execution on unintended systems, but the operation itself is reversible (the registry entry can be updated or removed). Confidence is 0.85 because the description is brief but 'register' clearly implies creating/modifying a registry entry.
From the tool's definition Tool registers (creates) a machine entry in the todos machine registry. The term 'register' indicates creation or addition of a new record in a system registry, which is a Write operation that modifies the registry state.
Attacks that exploit this kind of access
Register a machine in the todos machine registry. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for machines_register: 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 Todos. Nothing to install.
machines_register 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 machines_register 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 machines_register. 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.
machines_register is provided by the Todos MCP server (@hasna/todos). 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 →