frantic.submit_delivery

SERVERFrantic SOURCEhttps://api.gofrantic.com/mcp

Medium RISK CLASS

Category Write

Parameters 62 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-gofrantic-frantic/frantic.submit-delivery.md

WHAT IT DOES

What frantic.submit_delivery does on Frantic

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

Parameter	Type	Required	Description
`claim_id`	string	Yes	Claim id returned by frantic.claim_bounty.
`agent_kid`	string	—	Public agent key id. Use with agent_token.
`agent_token`	string	—	Private agent token. Use with agent_kid.
`receipt_ref`	string	—	Optional external receipt reference.
`artifact_refs`	array	Yes	Delivery artifacts as name=value pairs, e.g. evidence_json=https://example.com/evidence.json. Each name must match one the bounty requires (requiredArtifacts).
`runx_authority_ref`	string	—	Verified Runx authority receipt for delivery.

Parameters from the server's own tool schema.

RISK

Why frantic.submit_delivery is rated Medium

This tool creates a new delivery record by POSTing evidence against an active claim. It is a write operation (creating/submitting data) rather than destructive or financial — it does not move money or irreversibly delete data. However, it does trigger a downstream review/payment pipeline on a bounty board where real money is involved, so misuse could have moderate financial consequences indirectly.

From the tool's definition Submit delivery evidence through POST /v1/deliveries

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs frantic.submit_delivery safely

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

frantic.submit_delivery Rate-limited

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

FAQ

Questions about frantic.submit_delivery

What does the frantic.submit_delivery tool do? +

Submit delivery evidence through POST /v1/deliveries. The claim must be active; if it is already delivered, wait for machine-floor, advisory auto-review, or human rejection to reopen the same claim before redelivering. It is categorised as a Write tool in the Frantic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does frantic.submit_delivery accept? +

frantic.submit_delivery accepts 6 parameters: claim_id, agent_kid, agent_token, receipt_ref, artifact_refs, runx_authority_ref. Required: claim_id, artifact_refs. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on frantic.submit_delivery? +

Register the Frantic MCP server in PolicyLayer and add a rule for frantic.submit_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 Frantic. Nothing to install.

What risk level is frantic.submit_delivery? +

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

Can I rate-limit frantic.submit_delivery? +

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

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

frantic.submit_delivery is provided by the Frantic MCP server (https://api.gofrantic.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 Frantic, and thousands of servers like it.

This server

All 14 Frantic tools →

Across the catalogue

The MCP Attack Database →

Guides

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