deal_accept_terms
Locks in the CURRENT terms of the negotiation exactly as they stand and creates a permanent, immutable Contract between the two agents. Only the agent whose turn it is may accept — meaning you can only accept terms the other agent just proposed to you, never your own last offer. This cannot be un...
This record as markdown: /tools/com-focxle-afos/deal-accept-terms.md
What deal_accept_terms does on AFOS — Agentic Financial OS
AI agents use deal_accept_terms to commit financial operations through AFOS — Agentic Financial OS, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
version | integer | Yes | The negotiation's current version, as last read. |
negotiation_id | string | Yes |
Parameters from the server's own tool schema.
Why deal_accept_terms is rated Critical
Locks financial contract terms permanently and irreversibly between agents, committing financial obligations.
From the tool's definition creates a permanent, immutable Contract...cannot be undone or edited afterward
Attacks that exploit this kind of access
The rule that runs deal_accept_terms 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 deal_accept_terms, this is the rule to start with:
Any call to deal_accept_terms is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AFOS — Agentic Financial OS, apply this rule, and every deal_accept_terms call is checked against it from then on.
Questions about deal_accept_terms
Locks in the CURRENT terms of the negotiation exactly as they stand and creates a permanent, immutable Contract between the two agents. Only the agent whose turn it is may accept — meaning you can only accept terms the other agent just proposed to you, never your own last offer. This cannot be undone or edited afterward; use deal_propose_terms instead if you want different terms. It is categorised as a Financial tool in the AFOS — Agentic Financial OS MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
deal_accept_terms accepts 2 parameters: version, negotiation_id. Required: version, negotiation_id. The full parameter table on this page comes from the server's own tool schema.
Register the AFOS — Agentic Financial OS MCP server in PolicyLayer and add a rule for deal_accept_terms: 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.
deal_accept_terms is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deal_accept_terms 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.
Set action: deny in the PolicyLayer policy for deal_accept_terms. 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.
deal_accept_terms 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.
More on AFOS — Agentic Financial OS, and thousands of servers like it.
Across the catalogue