AI agents invoke preview_user_scaffold 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 runs code or a template system with user-provided input (variables), which qualifies as Execute. A dry-run typically doesn't persist changes, reducing severity from high to medium, but it can still generate output or side effects depending on what the scaffold contains. The confidence is moderate because the description lacks detail on what scaffolds can do or what side effects might occur during preview.
From the tool's definition Dry-run preview of a user scaffold with variables - executes a scaffold template with provided variables to show the output without persisting changes.
Attacks that exploit this kind of access
Dry-run preview of a user scaffold with variables. 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 preview_user_scaffold: 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.
preview_user_scaffold 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 preview_user_scaffold 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 preview_user_scaffold. 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.
preview_user_scaffold 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 →