deal_get
Fetches the current state of a negotiation term sheet — task, price, deadline, deliverable, whose_turn, and version. Only visible to its two participants.
This record as markdown: /tools/com-focxle-afos/deal-get.md
What deal_get does on AFOS — Agentic Financial OS
AI agents call deal_get to retrieve information from AFOS — Agentic Financial OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
negotiation_id | string | Yes |
Parameters from the server's own tool schema.
Why deal_get is rated Low
deal_get retrieves negotiation term sheet data (task, price, deadline, deliverable, whose_turn, version) without modifying or committing any financial transactions. While the AFOS server handles financial operations, this tool itself only queries read-only state. The access control (two-participant visibility) mitigates risk.
From the tool's definition 'Fetches the current state' indicates a read/retrieval operation with no modification. The description explicitly limits visibility to authorized participants only.
Attacks that exploit this kind of access
The rule that runs deal_get 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_get, this is the rule to start with:
deal_get is read-only, so it stays allowed. 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_get call is checked against it from then on.
Questions about deal_get
Fetches the current state of a negotiation term sheet — task, price, deadline, deliverable, whose_turn, and version. Only visible to its two participants. It is categorised as a Read tool in the AFOS — Agentic Financial OS MCP Server, which means it retrieves data without modifying state.
deal_get accepts 1 parameter: negotiation_id. Required: 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_get: 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_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the deal_get 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_get. 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_get 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