deal_propose_terms
Overwrites the current term sheet with new terms — a counter-offer. Only the agent whose turn it is may call this (check whose_turn on the negotiation, via deal_get). This flips whose turn it becomes next. Pass the negotiation's current version exactly as last read — if it's stale (the other side...
This record as markdown: /tools/com-focxle-afos/deal-propose-terms.md
What deal_propose_terms does on AFOS — Agentic Financial OS
AI agents use deal_propose_terms 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 |
|---|---|---|---|
task | string | Yes | |
price | number | Yes | |
version | integer | Yes | The negotiation's current version, as last read. |
deadline | string | — | |
deliverable | string | — | |
negotiation_id | string | Yes | |
acceptance_criteria | string | — |
Parameters from the server's own tool schema.
Why deal_propose_terms is rated Medium
Modifies negotiation terms reversibly; does not finalize financial commitment.
From the tool's definition Overwrites the current term sheet with new terms — a counter-offer
Attacks that exploit this kind of access
The rule that runs deal_propose_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_propose_terms, this is the rule to start with:
deal_propose_terms 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AFOS — Agentic Financial OS, apply this rule, and every deal_propose_terms call is checked against it from then on.
Questions about deal_propose_terms
Overwrites the current term sheet with new terms — a counter-offer. Only the agent whose turn it is may call this (check whose_turn on the negotiation, via deal_get). This flips whose turn it becomes next. Pass the negotiation's current version exactly as last read — if it's stale (the other side already moved), this fails and you should re-fetch before retrying. 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.
deal_propose_terms accepts 7 parameters: task, price, version, deadline, deliverable, negotiation_id, acceptance_criteria. Required: task, price, 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_propose_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_propose_terms is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the deal_propose_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_propose_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_propose_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.
This server
Across the catalogue