confirm_delivery

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

Medium RISK CLASS

Category Write

Parameters 53 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/confirm-delivery.md

WHAT IT DOES

What confirm_delivery does on Gateway

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

Parameter	Type	Required
`note`	string	—
`handle`	string	Yes
`secret`	string	—
`verdict`	string	Yes
`order_id`	integer	Yes

Parameters from the server's own tool schema.

RISK

Why confirm_delivery is rated Medium

This tool writes a verdict record to an exchange/marketplace system. While it modifies seller standing (which could be seen as destructive to reputation), it is a reversible audit record creation rather than a deletion. However, the side effect of lowering seller standing and the financial context (post-purchase on an Exchange) make this high severity.

From the tool's definition record your verdict on what you received: 'confirmed' or 'disputed' — a dispute has teeth — it lowers the seller's standing — One verdict per order

Risk signalsHandles credentials or secrets (secret)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs confirm_delivery safely

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

confirm_delivery Rate-limited

confirm_delivery 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": {
    "confirm_delivery": {
      "limits": [
        {
          "counter": "confirm_delivery_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 Gateway, apply this rule, and every confirm_delivery call is checked against it from then on.

FAQ

Questions about confirm_delivery

What does the confirm_delivery tool do? +

After buying on the Exchange, record your verdict on what you received: 'confirmed' (the delivery matched the listing) or 'disputed' (it didn't). A dispute has teeth — it lowers the seller's standing — and it's auditable because the exact delivered payload is on file. One verdict per order; registered buyer + secret required. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does confirm_delivery accept? +

confirm_delivery accepts 5 parameters: note, handle, secret, verdict, order_id. Required: handle, verdict, order_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on confirm_delivery? +

Register the Gateway MCP server in PolicyLayer and add a rule for confirm_delivery: 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 Gateway. Nothing to install.

What risk level is confirm_delivery? +

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

Can I rate-limit confirm_delivery? +

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

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

confirm_delivery is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools →

Across the catalogue

The MCP Attack Database →

Guides

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