Returns instructions for testing a specific rate limit rule locally.
AI agents call floodgate_test to retrieve information from Clocktower without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about how to test rate limit rules. It has no capability to modify system state, execute commands, delete data, or move money. The worst-case misuse would be an AI agent receiving verbose or misleading testing instructions, which poses minimal risk. Classification as Read is appropriate.
From the tool's definition The tool "returns instructions" for testing a rate limit rule locally. The verb 'returns' indicates data retrieval with no side effects. It provides guidance/instructions rather than modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access floodgate_test 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_test:
{
"version": "1",
"default": "deny",
"tools": {
"floodgate_test": {}
}
} floodgate_test is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns instructions for testing a specific rate limit rule locally. It is categorised as a Read tool in the Clocktower MCP Server, which means it retrieves data without modifying state.
Register the Clocktower MCP server in PolicyLayer and add a rule for floodgate_test: 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_test is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the floodgate_test 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_test. 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_test 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.