util_batch_rate_limit_plan
Batch Rate Limit Plan calculates dispatch duration from request count and rate window from bounded caller-supplied values without an external provider. Call Batch Rate Limit Plan before an agent hands structured data or a batch plan to a downstream tool with a stricter contract. Returns the bound...
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/util-batch-rate-limit-plan.md
What util_batch_rate_limit_plan does on Delx Protocol — Agent Recovery & Continuity
AI agents use util_batch_rate_limit_plan to create or update resources in Delx Protocol — Agent Recovery & Continuity, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Protocol — Agent Recovery & Continuity environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | Yes | Limit supplied to Batch Rate Limit Plan; used only for this bounded calculation and processed in memory without retention. |
request_count | integer | Yes | Request Count supplied to Batch Rate Limit Plan; used only for this bounded calculation and processed in memory without retention. |
window_seconds | integer | Yes | Window Seconds supplied to Batch Rate Limit Plan; used only for this bounded calculation and processed in memory without retention. |
Parameters from the server's own tool schema.
Why util_batch_rate_limit_plan is rated Medium
An AI agent can call util_batch_rate_limit_plan faster than any human can review: one bad instruction and it creates or modifies resources in Delx Protocol — Agent Recovery & Continuity by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs util_batch_rate_limit_plan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_batch_rate_limit_plan, this is the rule to start with:
util_batch_rate_limit_plan 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every util_batch_rate_limit_plan call is checked against it from then on.
Questions about util_batch_rate_limit_plan
Batch Rate Limit Plan calculates dispatch duration from request count and rate window from bounded caller-supplied values without an external provider. Call Batch Rate Limit Plan before an agent hands structured data or a batch plan to a downstream tool with a stricter contract. Returns the bounded transformation or validation finding with counts, normalized values, and a versioned result contract for Batch Rate Limit Plan as versioned deterministic JSON. Limitation: Processes bounded caller-supplied data in memory only; it performs no file fetch, database write, code execution, or retention. It is categorised as a Write tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
util_batch_rate_limit_plan accepts 3 parameters: limit, request_count, window_seconds. Required: limit, request_count, window_seconds. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for util_batch_rate_limit_plan: 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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
util_batch_rate_limit_plan 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 util_batch_rate_limit_plan 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 util_batch_rate_limit_plan. 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.
util_batch_rate_limit_plan is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue