Medium Risk

sc_todo_complete

Mark a task as completed.

Part of the Mcp Spec Cli server.

sc_todo_complete can modify Mcp Spec Cli data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MCP SPEC CLI →

Free to start. No card required.

AI agents use sc_todo_complete to create or modify resources in Mcp Spec Cli. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call sc_todo_complete repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Spec Cli.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "sc_todo_complete": {
      "limits": [
        {
          "counter": "sc_todo_complete_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Mcp Spec Cli policy for all 16 tools.

Get this rule live on your own Mcp Spec Cli server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCP SPEC CLI →

View all 16 tools →

These attack patterns abuse exactly the kind of access sc_todo_complete gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so sc_todo_complete only ever does what you allow.

SECURE MCP SPEC CLI →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the sc_todo_complete tool do? +

Mark a task as completed.. It is categorised as a Write tool in the Mcp Spec Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sc_todo_complete? +

Register the Mcp Spec Cli MCP server in PolicyLayer and add a rule for sc_todo_complete: 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.

What risk level is sc_todo_complete? +

sc_todo_complete is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sc_todo_complete? +

Yes. Add a rate_limit block to the sc_todo_complete 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.

How do I block sc_todo_complete completely? +

Set action: deny in the PolicyLayer policy for sc_todo_complete. 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.

What MCP server provides sc_todo_complete? +

sc_todo_complete 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.

Enforce policy on every Mcp Spec Cli tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.