Adds a new rate limit rule to an existing floodgate.config.ts file.
AI agents use floodgate_add_rule 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.
The tool creates or modifies configuration data (rate limit rules) in a reversible manner. While rate limit rules can affect system behavior, the action itself is reversible—rules can be modified or removed. This is a Write operation rather than Execute because it modifies configuration data rather than triggering active operations.
From the tool's definition Tool name contains 'add' and description states 'Adds a new rate limit rule to an existing floodgate.config.ts file', indicating creation/modification of configuration data.
Documented attack patterns abuse exactly the kind of access floodgate_add_rule gives an agent:
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 floodgate_add_rule:
{
"version": "1",
"default": "deny",
"tools": {
"floodgate_add_rule": {
"limits": [
{
"counter": "floodgate_add_rule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} floodgate_add_rule 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.
Free to start. No card required.
Adds a new rate limit rule to an existing floodgate.config.ts file. 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.
Register the Clocktower MCP server in PolicyLayer and add a rule for floodgate_add_rule: 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.
floodgate_add_rule 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 floodgate_add_rule 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 floodgate_add_rule. 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.
floodgate_add_rule 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.
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.