Mint an ephemeral api_key for a sub-agent dispatch. The raw_key is returned ONCE — pass it to the sub-agent via its launch arguments, never store it in env vars. The key expires after expires_in_seconds.
Part of the Loopctl server.
Free to start. No card required.
AI agents call dispatch to retrieve information from Loopctl without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though dispatch only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"dispatch": {}
}
}See the full Loopctl policy for all 52 tools.
These attack patterns abuse exactly the kind of access dispatch gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Mint an ephemeral api_key for a sub-agent dispatch. The raw_key is returned ONCE — pass it to the sub-agent via its launch arguments, never store it in env vars. The key expires after expires_in_seconds.. It is categorised as a Read tool in the Loopctl MCP Server, which means it retrieves data without modifying state.
Register the Loopctl MCP server in PolicyLayer and add a rule for dispatch: 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 Loopctl. Nothing to install.
dispatch 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 dispatch 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 dispatch. 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.
dispatch is provided by the Loopctl MCP server (loopctl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 52 Loopctl tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.