util_agent_delivery_acceptance_gate

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

Low RISK CLASS

Category Read

Parameters 55 required

Recommended Allowedsee 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-acceptance-gate.md

WHAT IT DOES

What util_agent_delivery_acceptance_gate does on Delx Mcp A2a

AI agents call util_agent_delivery_acceptance_gate to retrieve information from Delx Mcp A2a 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
`complete`	boolean	Yes	Complete supplied to Agent Delivery Acceptance Gate; used only for this bounded calculation and processed in memory without retention.
`within_sla`	boolean	Yes	Within Sla supplied to Agent Delivery Acceptance Gate; used only for this bounded calculation and processed in memory without retention.
`schema_valid`	boolean	Yes	Schema Valid supplied to Agent Delivery Acceptance Gate; used only for this bounded calculation and processed in memory without retention.
`payment_match`	boolean	Yes	Payment Match supplied to Agent Delivery Acceptance Gate; used only for this bounded calculation and processed in memory without retention.
`provenance_present`	boolean	Yes	Provenance Present supplied to Agent Delivery Acceptance Gate; 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_acceptance_gate is rated Low

Even though util_agent_delivery_acceptance_gate 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

RECOMMENDED RULE

The rule that runs util_agent_delivery_acceptance_gate 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_acceptance_gate, this is the rule to start with:

util_agent_delivery_acceptance_gate Allowed

util_agent_delivery_acceptance_gate is read-only, so it stays allowed. 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_acceptance_gate": {}
  }
}

ALLOW ONLY 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_acceptance_gate call is checked against it from then on.

FAQ

Questions about util_agent_delivery_acceptance_gate

What does the util_agent_delivery_acceptance_gate tool do? +

Agent Delivery Acceptance Gate combines required delivery checks into one fail-closed acceptance decision from bounded caller-supplied values without an external provider. Call Agent Delivery Acceptance Gate 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 Acceptance Gate 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 Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.

What parameters does util_agent_delivery_acceptance_gate accept? +

util_agent_delivery_acceptance_gate accepts 5 parameters: complete, within_sla, schema_valid, payment_match, provenance_present. Required: complete, within_sla, schema_valid, payment_match, provenance_present. 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_acceptance_gate? +

Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_agent_delivery_acceptance_gate: 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_acceptance_gate? +

util_agent_delivery_acceptance_gate is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit util_agent_delivery_acceptance_gate? +

Yes. Add a rate_limit block to the util_agent_delivery_acceptance_gate 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_acceptance_gate completely? +

Set action: deny in the PolicyLayer policy for util_agent_delivery_acceptance_gate. 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_acceptance_gate? +

util_agent_delivery_acceptance_gate 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

aiva_get_delivery_schedule on AIVA MCP Server →get_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →