reject_negotiation

Reject a negotiation

SERVERMIDAS Protocol SOURCEhttps://mcp.midasprotocol.org/mcp

Critical RISK CLASS

Category Financial

Parameters 11 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/reject-negotiation.md

WHAT IT DOES

What reject_negotiation does on MIDAS Protocol

AI agents use reject_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.

RISK

Why reject_negotiation is rated Critical

Rejecting a negotiation has direct financial consequences — it terminates a potentially binding financial agreement (e.g., loan, escrow, payment deal). On a financial infrastructure platform alongside tools like accept_negotiation, borrow, and book_and_pay, this action affects financial obligations and outcomes for involved parties, placing it firmly in the Financial category.

From the tool's definition 'Reject a negotiation' on a server described as 'Complete financial infrastructure for AI agents — payments, lending, escrow & more.' with sibling tools including accept_negotiation, borrow, book_and_pay, cancel_subscription

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reject_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 reject_negotiation, this is the rule to start with:

reject_negotiation Approval-gated

Any call to reject_negotiation is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reject_negotiation": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect MIDAS Protocol, apply this rule, and every reject_negotiation call is checked against it from then on.

FAQ

Questions about reject_negotiation

What does the reject_negotiation tool do? +

Reject a 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.

What parameters does reject_negotiation accept? +

reject_negotiation accepts 1 parameter: negotiationId. Required: negotiationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on reject_negotiation? +

Register the MIDAS Protocol MCP server in PolicyLayer and add a rule for reject_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.

What risk level is reject_negotiation? +

reject_negotiation is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit reject_negotiation? +

Yes. Add a rate_limit block to the reject_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.

How do I block reject_negotiation completely? +

Set action: deny in the PolicyLayer policy for reject_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.

What MCP server provides reject_negotiation? +

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

KEEP EXPLORING

More on MIDAS Protocol, and thousands of servers like it.

This server

All 44 MIDAS Protocol tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →