sifter_init

THE RISK

Medium Risk

Why sifter_init needs a policy

This tool creates a new configuration file in the project directory. It's a Write operation (file creation) rather than Execute since it's scaffolding a static config file, not running code. The blast radius is low as it only creates a starter config file that can be easily removed or modified.

From the tool's definition Scaffolds a searchcraft.config.ts in a project directory with a starter search schema

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

POLICY

How to control sifter_init

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sifter_init": {
      "limits": [
        {
          "counter": "sifter_init_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

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.

LIMIT 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 clocktower_add_job Add a job definition to an existing croncall config file. Write flagpost_add_flag Adds a new feature flag definition to an existing flagpost.config.ts file.

All 26 Clocktower tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sifter_init

What does the sifter_init tool do? +

Scaffolds a searchcraft.config.ts in a project directory with a starter search schema. Detects pressroom integration if present. 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 sifter_init? +

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

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

Can I rate-limit sifter_init? +

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

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

sifter_init 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 →