human_approve_negotiation
Approve a negotiation exceeding the automatic threshold
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/human-approve-negotiation.md
What human_approve_negotiation does on MIDAS Protocol
AI agents use human_approve_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 |
|---|---|---|---|
negotiationId | string | Yes |
Parameters from the server's own tool schema.
Why human_approve_negotiation is rated Critical
This tool approves financial negotiations that have exceeded automatic approval limits, directly committing to financial obligations or agreements. Given the context of a financial infrastructure platform handling payments, lending, and escrow, approving a negotiation likely triggers binding financial commitments.
From the tool's definition Approve a negotiation exceeding the automatic threshold
Attacks that exploit this kind of access
The rule that runs human_approve_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 human_approve_negotiation, this is the rule to start with:
Any call to human_approve_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 human_approve_negotiation call is checked against it from then on.
Questions about human_approve_negotiation
Approve a negotiation exceeding the automatic threshold. 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.
human_approve_negotiation accepts 1 parameter: negotiationId. Required: 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 human_approve_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.
human_approve_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 human_approve_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 human_approve_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.
human_approve_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