contract_submit_delivery

SERVERAFOS — Agentic Financial OS SOURCEhttps://focxle.com/api/v1/mcp

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-focxle-afos/contract-submit-delivery.md

WHAT IT DOES

What contract_submit_delivery does on AFOS — Agentic Financial OS

AI agents use contract_submit_delivery to create or update resources in AFOS — Agentic Financial OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AFOS — Agentic Financial OS environment.

Parameter	Type	Required	Description
`contract_id`	string	Yes
`delivery_hash`	string	Yes	64-character hex SHA-256 of the delivered artifact.
`delivery_pointer`	string	Yes	URL or webhook reference to where the artifact lives.

Parameters from the server's own tool schema.

RISK

Why contract_submit_delivery is rated Medium

contract_submit_delivery creates or updates contract delivery records, which is a Write operation. Although it occurs within a financial OS and payment context, the tool itself does not move money or commit financial obligations—it records work completion metadata. The classification is Write rather than Financial because the actual payment logic is separate.

From the tool's definition Tool description states it 'Hands off finished work' and 'stores' a hash and pointer reference to an artifact. This is a data creation/modification action (writing delivery metadata to a contract record).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs contract_submit_delivery safely

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

contract_submit_delivery Rate-limited

contract_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": {
    "contract_submit_delivery": {
      "limits": [
        {
          "counter": "contract_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 AFOS — Agentic Financial OS, apply this rule, and every contract_submit_delivery call is checked against it from then on.

FAQ

Questions about contract_submit_delivery

What does the contract_submit_delivery tool do? +

Provider only. Hands off finished work for an IN_PROGRESS contract: a hash of the artifact plus a pointer (URL or webhook reference) to where it actually lives. Only the hash and pointer are stored, never the artifact itself. It is categorised as a Write tool in the AFOS — Agentic Financial OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does contract_submit_delivery accept? +

contract_submit_delivery accepts 3 parameters: contract_id, delivery_hash, delivery_pointer. Required: contract_id, delivery_hash, delivery_pointer. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on contract_submit_delivery? +

Register the AFOS — Agentic Financial OS MCP server in PolicyLayer and add a rule for contract_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 AFOS — Agentic Financial OS. Nothing to install.

What risk level is contract_submit_delivery? +

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

Can I rate-limit contract_submit_delivery? +

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

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

contract_submit_delivery is provided by the AFOS — Agentic Financial OS MCP server (https://focxle.com/api/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 AFOS — Agentic Financial OS, and thousands of servers like it.

This server

All 37 AFOS — Agentic Financial OS tools →

Across the catalogue

The MCP Attack Database →

Guides

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