AI agents invoke run_agent_workflow_demo 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 pre-defined agent workflows and processes, which constitutes code/automation execution. While it operates on an 'ephemeral database' (reducing persistence concerns), it still triggers external operations and agent behaviors whose side effects depend on workflow configuration. This fits Execute rather than Write because it runs agents/scripts rather than merely creating/modifying data directly.
From the tool's definition Tool description states it 'Run[s] a scripted local agent workflow demo' - the verb 'Run' indicates execution of code/scripts.
Attacks that exploit this kind of access
Run a scripted local agent workflow demo (agents, projects, tasks, runs) using an ephemeral 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 run_agent_workflow_demo: 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.
run_agent_workflow_demo 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 run_agent_workflow_demo 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 run_agent_workflow_demo. 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.
run_agent_workflow_demo 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 →