dispute_outcome · Basis MCP Server MCP: Risk & Policy

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.

WHY IT NEEDS A POLICY

Why dispute_outcome needs a policy

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 Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Basis MCP Server, so you can run agents against it safely.

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.