score_task · Todos MCP: Risk & Policy

WHAT IT DOES

What score_task does on Todos

AI agents use score_task to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.

WHY IT NEEDS A POLICY

Why score_task needs a policy

Scoring a completed task modifies existing task data (adds/updates a score attribute). This is a reversible write operation — the score can presumably be changed again. It does not delete data, execute code, or involve finances. Confidence is moderate because the description is brief and doesn't clarify whether scoring triggers irreversible downstream effects.

From the tool's definition Score a completed task

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

score_task Rate-limited

score_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "score_task": {
      "limits": [
        {
          "counter": "score_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Todos, so you can run agents against it safely.

FAQ

Questions about score_task

What does the score_task tool do? +

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

How do I enforce a policy on score_task? +

Register the Todos MCP server in PolicyLayer and add a rule for score_task: 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.

What risk level is score_task? +

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

Can I rate-limit score_task? +

Yes. Add a rate_limit block to the score_task 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 score_task completely? +

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

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