clocktower_schedule

THE RISK

Low Risk

Why clocktower_schedule needs a policy

The tool only reads and parses a config file to display upcoming scheduled job runs. It does not modify, execute, or delete anything — purely a read/query operation with minimal blast radius.

From the tool's definition "List upcoming job runs parsed from a croncall config file"

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

POLICY

How to control clocktower_schedule

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 clocktower_schedule:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clocktower_schedule": {}
  }
}

clocktower_schedule is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Clocktower tools

Execute darkroom_optimize Processes images in a directory using shutterbox image pipeline. Scans the directory for i Write clocktower_init Scaffold a croncall.config.ts file in the target project directory. Write darkroom_init Creates shutterbox.config.ts in a project directory. Scaffolds a starter config with thumb Write flagpost_init Creates flagpost.config.ts in a project directory. Scaffolds a starter config with an exam Write floodgate_init Creates floodgate.config.ts in a project directory. Scaffolds a starter config with defaul Write lockbox_init Initialize lockbox in a project. Creates .vaultbox-key, .secrets/ directory, and updates . Write sifter_init Scaffolds a searchcraft.config.ts in a project directory with a starter search schema. Det Write clocktower_add_job Add a job definition to an existing croncall config file.

All 26 Clocktower tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about clocktower_schedule

What does the clocktower_schedule tool do? +

List upcoming job runs parsed from a croncall config file. It is categorised as a Read tool in the Clocktower MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on clocktower_schedule? +

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

clocktower_schedule is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit clocktower_schedule? +

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

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

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

CHECK YOUR STACK →