set_secret_safety · Todos MCP: Risk & Policy

WHAT IT DOES

What set_secret_safety does on Todos

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

This tool creates or modifies redaction safety configurations (regex patterns and object keys) that are stored locally. This is a reversible modification of system configuration, fitting the Write category. Severity is medium because misconfiguration could expose secrets or prevent legitimate redaction, affecting security posture but not directly moving money, deleting data, or executing arbitrary code.

From the tool's definition Tool name "set_secret_safety" with description "Add local secret redaction regex patterns or object key names" indicates creating or modifying redaction configuration. The verb "Add" and action of storing patterns/keys confirms write semantics.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_secret_safety Rate-limited

set_secret_safety 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": {
    "set_secret_safety": {
      "limits": [
        {
          "counter": "set_secret_safety_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 set_secret_safety

What does the set_secret_safety tool do? +

Add local secret redaction regex patterns or object key names. 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 set_secret_safety? +

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

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

Can I rate-limit set_secret_safety? +

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

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

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