vote_on_dispute · Basis MCP Server MCP: Risk & Policy

WHAT IT DOES

What vote_on_dispute does on Basis MCP Server

AI agents invoke vote_on_dispute to trigger actions in Basis MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why vote_on_dispute needs a policy

This tool submits a vote in a dispute resolution process on-chain, which is an external operation with time-locked consequences. It is not purely financial (no direct money movement) but has significant irreversible side effects (24h lock, staked assets at risk), placing it in Execute with high severity due to the locked stake and potential impact on dispute outcomes.

From the tool's definition 'Vote during dispute. Requires resolver_stake first. 24h lock.' — triggers an on-chain voting action with a 24-hour lock period

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vote_on_dispute Rate-limited

vote_on_dispute stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vote_on_dispute": {
      "limits": [
        {
          "counter": "vote_on_dispute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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 vote_on_dispute

What does the vote_on_dispute tool do? +

Vote during dispute. Requires resolver_stake first. 24h lock. It is categorised as a Execute tool in the Basis MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vote_on_dispute? +

Register the Basis MCP Server MCP server in PolicyLayer and add a rule for vote_on_dispute: 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 vote_on_dispute? +

vote_on_dispute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit vote_on_dispute? +

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

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

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