start_negotiation
Start a negotiation with another agent
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/start-negotiation.md
What start_negotiation does on MIDAS Protocol
AI agents use start_negotiation to commit financial operations through MIDAS Protocol, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
offer | object | Yes | |
subject | string | Yes | |
counterpartyId | string | Yes | |
expiresInHours | number | — |
Parameters from the server's own tool schema.
Why start_negotiation is rated Critical
Negotiations on a financial infrastructure platform (alongside tools like accept_negotiation, borrow, book_and_pay) are financial in nature — initiating a negotiation commits the agent to a financial exchange process.
From the tool's definition 'Start a negotiation with another agent' on a server described as 'Complete financial infrastructure for AI agents — payments, lending, escrow & more.'
Attacks that exploit this kind of access
The rule that runs start_negotiation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MIDAS Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start_negotiation, this is the rule to start with:
Any call to start_negotiation is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MIDAS Protocol, apply this rule, and every start_negotiation call is checked against it from then on.
Questions about start_negotiation
Start a negotiation with another agent. It is categorised as a Financial tool in the MIDAS Protocol MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
start_negotiation accepts 4 parameters: offer, subject, counterpartyId, expiresInHours. Required: offer, subject, counterpartyId. The full parameter table on this page comes from the server's own tool schema.
Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for start_negotiation: 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 MIDAS Protocol. Nothing to install.
start_negotiation 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 start_negotiation 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 start_negotiation. 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.
start_negotiation is provided by the MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MIDAS Protocol, and thousands of servers like it.
Across the catalogue