Mark a task as being actively worked on.
Part of the Mcp Spec Cli server.
Free to start. No card required.
AI agents invoke sc_todo_start to trigger processes or run actions in Mcp Spec Cli. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
sc_todo_start can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"sc_todo_start": {
"limits": [
{
"counter": "sc_todo_start_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Mcp Spec Cli policy for all 16 tools.
These attack patterns abuse exactly the kind of access sc_todo_start gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Mark a task as being actively worked on.. It is categorised as a Execute tool in the Mcp Spec Cli MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Spec Cli MCP server in PolicyLayer and add a rule for sc_todo_start: 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 Spec Cli. Nothing to install.
sc_todo_start 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 sc_todo_start 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 sc_todo_start. 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.
sc_todo_start is provided by the Mcp Spec Cli MCP server (mcp-spec-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Mcp Spec Cli tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.