updown_cancel_stalled
Public cancel of a stalled UPDOWN round (settle window expired). Anyone can call after endTime + FINALIZE_WINDOW.
This record as markdown: /tools/launch-on-basis-mcp-ts/updown-cancel-stalled.md
What updown_cancel_stalled does on Basis MCP Server
AI agents invoke updown_cancel_stalled 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 updown_cancel_stalled is rated High
This tool executes a blockchain transaction to cancel a stalled prediction market round. While it has some destructive characteristics (cancelling the round), the action is a permissioned recovery mechanism available to anyone after a timeout window, and cancellation of a stalled round is likely a recoverable state (funds returned to participants).
From the tool's definition 'Public cancel of a stalled UPDOWN round (settle window expired). Anyone can call after endTime + FINALIZE_WINDOW.' — triggers an on-chain cancellation action on a prediction market round.
Attacks that exploit this kind of access
The rule that runs updown_cancel_stalled 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_cancel_stalled, this is the rule to start with:
updown_cancel_stalled 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every updown_cancel_stalled call is checked against it from then on.
Questions about updown_cancel_stalled
Public cancel of a stalled UPDOWN round (settle window expired). Anyone can call after endTime + FINALIZE_WINDOW. 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.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for updown_cancel_stalled: 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_cancel_stalled is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the updown_cancel_stalled 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_cancel_stalled. 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_cancel_stalled 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