run_release_checks · Todos MCP: Risk & Policy

WHAT IT DOES

What run_release_checks does on Todos

AI agents invoke run_release_checks 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.

WHY IT NEEDS A POLICY

Why run_release_checks needs a policy

This tool executes external operations (package release checks and supply-chain verification) that can affect systems and workflows. While not directly destructive or financial, execution of package checks could trigger builds, deployments, or security analyses with side effects dependent on the arguments.

From the tool's definition The tool name contains 'run' and the description explicitly states 'Run public package release and supply-chain hardening checks.' The verb 'Run' indicates execution of operations whose effects depend on the arguments provided (which checks to run, against…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_release_checks Rate-limited

run_release_checks stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_release_checks": {
      "limits": [
        {
          "counter": "run_release_checks_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 run_release_checks

What does the run_release_checks tool do? +

Run public package release and supply-chain hardening checks. 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.

How do I enforce a policy on run_release_checks? +

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

run_release_checks is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_release_checks? +

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

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

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