update_risk · Todos MCP: Risk & Policy

WHAT IT DOES

What update_risk does on Todos

AI agents use update_risk 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 update_risk needs a policy

This tool modifies (updates) an existing risk register entry reversibly. It is a Write operation because it creates or modifies data without irreversibly deleting it or executing arbitrary code. Severity is medium because misuse could lead to incorrect risk documentation, affecting project decision-making, but the impact is typically localized to the risk register itself and not financial or destructive.

From the tool's definition Tool name 'update_risk' and description 'Update a local risk register entry' indicate modification of existing data in a risk register.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_risk Rate-limited

update_risk 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": {
    "update_risk": {
      "limits": [
        {
          "counter": "update_risk_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 update_risk

What does the update_risk tool do? +

Update a local risk register entry. 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 update_risk? +

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

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

Can I rate-limit update_risk? +

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

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

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