set_secret_safety
Add local secret redaction regex patterns or object key names.
This record as markdown: /tools/todos/set-secret-safety.md
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 set_secret_safety is rated Medium
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
The rule that runs set_secret_safety safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_secret_safety, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every set_secret_safety call is checked against it from then on.
Questions about set_secret_safety
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.
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.
set_secret_safety is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on Todos, and thousands of servers like it.
This server
Across the catalogue