AI agents invoke simulate_agent_replay to trigger actions in Todos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes recorded agent contexts and run fixtures (simulating agent behavior and code execution), making it an Execute category tool. While the dry-run nature and lack of database mutations reduce severity below a typical Execute operation, replay of arbitrary recorded contexts could still pose risks if the recorded operations include harmful commands or side effects to external systems.
From the tool's definition Tool description states it performs a 'replay' of a 'recorded local agent context pack or run fixture', which involves executing/simulating recorded operations.
Attacks that exploit this kind of access
Dry-run replay a recorded local agent context pack or run fixture without mutating the task database. It is categorised as a Execute tool in the Todos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Todos MCP server in PolicyLayer and add a rule for simulate_agent_replay: 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.
simulate_agent_replay is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the simulate_agent_replay 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 simulate_agent_replay. 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.
simulate_agent_replay 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 →