util_batch_error_budget_check
Batch Error Budget Check checks failed item count and fraction against caller budgets from bounded caller-supplied values without an external provider. Call Batch Error Budget Check before an agent hands structured data or a batch plan to a downstream tool with a stricter contract. Returns the bo...
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/util-batch-error-budget-check.md
What util_batch_error_budget_check does on Delx Protocol — Agent Recovery & Continuity
AI agents call util_batch_error_budget_check to retrieve information from Delx Protocol — Agent Recovery & Continuity without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
total | integer | Yes | Total supplied to Batch Error Budget Check; used only for this bounded calculation and processed in memory without retention. |
failed | integer | Yes | Failed supplied to Batch Error Budget Check; used only for this bounded calculation and processed in memory without retention. |
maximum_failed | integer | Yes | Maximum Failed supplied to Batch Error Budget Check; used only for this bounded calculation and processed in memory without retention. |
maximum_failure_fraction | number | Yes | Maximum Failure Fraction supplied to Batch Error Budget Check; used only for this bounded calculation and processed in memory without retention. |
Parameters from the server's own tool schema.
Why util_batch_error_budget_check is rated Low
Even though util_batch_error_budget_check only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs util_batch_error_budget_check 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_error_budget_check, this is the rule to start with:
util_batch_error_budget_check is read-only, so it stays allowed. 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_error_budget_check call is checked against it from then on.
Questions about util_batch_error_budget_check
Batch Error Budget Check checks failed item count and fraction against caller budgets from bounded caller-supplied values without an external provider. Call Batch Error Budget Check 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 Error Budget Check 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 Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
util_batch_error_budget_check accepts 4 parameters: total, failed, maximum_failed, maximum_failure_fraction. Required: total, failed, maximum_failed, maximum_failure_fraction. 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_error_budget_check: 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_error_budget_check 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 util_batch_error_budget_check 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_error_budget_check. 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_error_budget_check 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