veto_outcome · Basis MCP Server MCP: Risk & Policy

WHAT IT DOES

What veto_outcome does on Basis MCP Server

AI agents invoke veto_outcome 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 veto_outcome needs a policy

This tool triggers an administrative action that overrides or cancels a proposed prediction market outcome. While not moving money directly, it alters the state of an active prediction market in a potentially irreversible way (vetoing an outcome can invalidate bets, affect payouts, and change market resolution).

From the tool's definition Veto a proposed market outcome (admin)

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

veto_outcome Rate-limited

veto_outcome 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": {
    "veto_outcome": {
      "limits": [
        {
          "counter": "veto_outcome_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 veto_outcome

What does the veto_outcome tool do? +

Veto a proposed market outcome (admin). 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 veto_outcome? +

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

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

Can I rate-limit veto_outcome? +

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

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

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