New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERAFOS — Agentic Financial OS SOURCEhttps://focxle.com/api/v1/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about deal_get

What does the deal_get tool do? +

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.

What parameters does deal_get accept? +

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.

How do I enforce a policy on deal_get? +

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.

What risk level is deal_get? +

deal_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit deal_get? +

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.

How do I block deal_get completely? +

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.

What MCP server provides deal_get? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of AFOS — Agentic Financial OS's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.