dispute_outcome

Dispute proposed outcome (5 USDB bond).

SERVERBasis MCP Server SOURCElaunch-on-basis/mcp-ts

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/launch-on-basis-mcp-ts/dispute-outcome.md

WHAT IT DOES

What dispute_outcome does on Basis MCP Server

AI agents use dispute_outcome to commit financial operations through Basis MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why dispute_outcome is rated Critical

This tool commits a financial obligation by posting a 5 USDB bond as part of a dispute mechanism in a prediction market. It directly moves or locks financial assets (USDB tokens), making it a Financial category action. Misuse could result in loss of the bonded funds or manipulation of prediction market outcomes, warranting a high severity rating.

From the tool's definition Dispute proposed outcome (5 USDB bond)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dispute_outcome safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dispute_outcome, this is the rule to start with:

dispute_outcome Approval-gated

Any call to dispute_outcome 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": {
    "dispute_outcome": {
      "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 Basis MCP Server, apply this rule, and every dispute_outcome call is checked against it from then on.

FAQ

Questions about dispute_outcome

What does the dispute_outcome tool do? +

Dispute proposed outcome (5 USDB bond). It is categorised as a Financial tool in the Basis MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on dispute_outcome? +

Register the Basis MCP Server MCP server in PolicyLayer and add a rule for dispute_outcome: 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 Basis MCP Server. Nothing to install.

What risk level is dispute_outcome? +

dispute_outcome 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 dispute_outcome? +

Yes. Add a rate_limit block to the dispute_outcome 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 dispute_outcome completely? +

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

dispute_outcome is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Basis MCP Server, and thousands of servers like it.

This server

All 204 Basis MCP Server 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 →