counter_offer
Send a counter-offer in an active negotiation
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/counter-offer.md
What counter_offer does on MIDAS Protocol
AI agents use counter_offer 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 | |
negotiationId | string | Yes |
Parameters from the server's own tool schema.
Why counter_offer is rated Critical
Counter-offers in a financial negotiation context commit the agent to financial terms and obligations. On a platform handling payments, lending, and escrow, sending a counter-offer can bind the agent to financial agreements, making this a Financial category tool with high severity due to potential for unauthorized financial commitments.
From the tool's definition 'Send a counter-offer in an active negotiation' 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 counter_offer 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 counter_offer, this is the rule to start with:
Any call to counter_offer 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 counter_offer call is checked against it from then on.
Questions about counter_offer
Send a counter-offer in an active negotiation. 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.
counter_offer accepts 2 parameters: offer, negotiationId. Required: offer, negotiationId. 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 counter_offer: 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.
counter_offer 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 counter_offer 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 counter_offer. 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.
counter_offer 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