updown_bet
Place a bullish or bearish bet on the current UPDOWN round. Auto-approves USDB and pre-checks balance + minBet client-side. Use slippage_percent for an optional minShares guard.
This record as markdown: /tools/launch-on-basis-mcp-ts/updown-bet.md
What updown_bet does on Basis MCP Server
AI agents use updown_bet 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 updown_bet is rated Critical
This tool places financial bets using USDB tokens on a prediction market, directly committing funds to a financial wager. It auto-approves token spending and executes on-chain transactions involving real monetary value, making it Financial category with critical severity due to potential for significant financial loss if misused.
From the tool's definition Place a bullish or bearish bet on the current UPDOWN round. Auto-approves USDB and pre-checks balance + minBet client-side.
Attacks that exploit this kind of access
The rule that runs updown_bet 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 updown_bet, this is the rule to start with:
Any call to updown_bet is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every updown_bet call is checked against it from then on.
Questions about updown_bet
Place a bullish or bearish bet on the current UPDOWN round. Auto-approves USDB and pre-checks balance + minBet client-side. Use slippage_percent for an optional minShares guard. 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.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for updown_bet: 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.
updown_bet is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the updown_bet 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.
Set action: deny in the PolicyLayer policy for updown_bet. 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.
updown_bet 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.
More on Basis MCP Server, and thousands of servers like it.
Across the catalogue