Medium Risk

lockbox_set

Set (encrypt and store) a secret in the lockbox.

How to control lockbox_set ↓

What lockbox_set does on Clocktower

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

Medium Risk

Why lockbox_set needs a policy

This tool creates or modifies data (storing encrypted secrets) with reversible effects—secrets can be updated or removed. While it handles sensitive data, the operation itself is a standard Write action (create/store). Severity is medium rather than low because misuse could expose or overwrite critical authentication credentials or API keys, but the encryption mitigates direct exposure risk.

From the tool's definition Tool name 'lockbox_set' and description 'Set (encrypt and store) a secret in the lockbox' indicate the tool creates or modifies encrypted secret data in storage.

Documented attack patterns abuse exactly the kind of access lockbox_set gives an agent:

How to control lockbox_set

PolicyLayer is an MCP gateway — it sits between your AI agents and Clocktower, and nothing reaches the server without passing your rules. This is the rule we recommend for lockbox_set:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lockbox_set": {
      "limits": [
        {
          "counter": "lockbox_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Clocktower — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about lockbox_set

What does the lockbox_set tool do? +

Set (encrypt and store) a secret in the lockbox. It is categorised as a Write tool in the Clocktower MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lockbox_set? +

Register the Clocktower MCP server in PolicyLayer and add a rule for lockbox_set: 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 Clocktower. Nothing to install.

What risk level is lockbox_set? +

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

Can I rate-limit lockbox_set? +

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

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

lockbox_set is provided by the Clocktower MCP server (sathergate/sathergate-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Clocktower tool call.

Start from Clocktower, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

26 Clocktower tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.