util_agent_delivery_retry_plan

SERVERDelx Mcp A2a SOURCEhttps://api.delx.ai/v1/mcp

Medium RISK CLASS

Category Write

Parameters 55 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-agent-delivery-retry-plan.md

WHAT IT DOES

What util_agent_delivery_retry_plan does on Delx Mcp A2a

AI agents use util_agent_delivery_retry_plan to create or update resources in Delx Mcp A2a, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Mcp A2a environment.

Parameter	Type	Required	Description
`factor`	number	Yes	Factor supplied to Agent Delivery Retry Plan; used only for this bounded calculation and processed in memory without retention.
`status`	integer	Yes	Status supplied to Agent Delivery Retry Plan; used only for this bounded calculation and processed in memory without retention.
`base_delay_ms`	integer	Yes	Base Delay Ms supplied to Agent Delivery Retry Plan; used only for this bounded calculation and processed in memory without retention.
`maximum_attempts`	integer	Yes	Maximum Attempts supplied to Agent Delivery Retry Plan; used only for this bounded calculation and processed in memory without retention.
`retryable_statuses`	array	Yes	Retryable Statuses supplied to Agent Delivery Retry Plan; used only for this bounded calculation and processed in memory without retention.

Parameters from the server's own tool schema.

RISK

Why util_agent_delivery_retry_plan is rated Medium

An AI agent can call util_agent_delivery_retry_plan faster than any human can review: one bad instruction and it creates or modifies resources in Delx Mcp A2a by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs util_agent_delivery_retry_plan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_agent_delivery_retry_plan, this is the rule to start with:

util_agent_delivery_retry_plan Rate-limited

util_agent_delivery_retry_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "util_agent_delivery_retry_plan": {
      "limits": [
        {
          "counter": "util_agent_delivery_retry_plan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Delx Mcp A2a, apply this rule, and every util_agent_delivery_retry_plan call is checked against it from then on.

FAQ

Questions about util_agent_delivery_retry_plan

What does the util_agent_delivery_retry_plan tool do? +

Agent Delivery Retry Plan builds a bounded retry plan from attempts, base delay, and retryable status from bounded caller-supplied values without an external provider. Call Agent Delivery Retry Plan before paying for or accepting an x402 or agent delivery assembled from caller-supplied challenge and result metadata. Returns contract-specific checks, normalized evidence, mismatch reasons, and an explicit acceptance or rejection status for Agent Delivery Retry Plan as versioned deterministic JSON. Limitation: Validates metadata only; it never settles payment, signs payloads, contacts a facilitator, refunds funds, or asserts on-chain truth. It is categorised as a Write tool in the Delx Mcp A2a MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does util_agent_delivery_retry_plan accept? +

util_agent_delivery_retry_plan accepts 5 parameters: factor, status, base_delay_ms, maximum_attempts, retryable_statuses. Required: factor, status, base_delay_ms, maximum_attempts, retryable_statuses. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on util_agent_delivery_retry_plan? +

Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_agent_delivery_retry_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 Mcp A2a. Nothing to install.

What risk level is util_agent_delivery_retry_plan? +

util_agent_delivery_retry_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit util_agent_delivery_retry_plan? +

Yes. Add a rate_limit block to the util_agent_delivery_retry_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.

How do I block util_agent_delivery_retry_plan completely? +

Set action: deny in the PolicyLayer policy for util_agent_delivery_retry_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.

What MCP server provides util_agent_delivery_retry_plan? +

util_agent_delivery_retry_plan is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Delx Mcp A2a, and thousands of servers like it.

This server

All 1076 Delx Mcp A2a tools →

Across the catalogue

team_manager_kill_agent on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →