updown_get_round
Get a specific UPDOWN round by id — or omit round_id to get the current round. Returns the full Round struct (startPrice/endPrice in 8-dec, pools/shares/seedBonus in 18-dec USDB, outcome enum 0=Pending,1=BullWins,2=BearWins,3=Canceled). Returns null if no rounds opened yet.
This record as markdown: /tools/launch-on-basis-mcp-ts/updown-get-round.md
What updown_get_round does on Basis MCP Server
AI agents call updown_get_round to retrieve information from Basis MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why updown_get_round is rated Low
This is a pure data retrieval operation for querying UPDOWN prediction market round information. It retrieves immutable historical or current state data and has no side effects. The tool merely queries and returns round metadata without creating, modifying, or destroying data.
From the tool's definition Tool description uses 'Get' verb and returns round data with no modification capabilities. Returns 'the full Round struct' with price, pool, and outcome information. No write, delete, execute, or financial operation is performed.
Attacks that exploit this kind of access
The rule that runs updown_get_round 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_get_round, this is the rule to start with:
updown_get_round is read-only, so it stays allowed. 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_get_round call is checked against it from then on.
Questions about updown_get_round
Get a specific UPDOWN round by id — or omit round_id to get the current round. Returns the full Round struct (startPrice/endPrice in 8-dec, pools/shares/seedBonus in 18-dec USDB, outcome enum 0=Pending,1=BullWins,2=BearWins,3=Canceled). Returns null if no rounds opened yet. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for updown_get_round: 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_get_round is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the updown_get_round 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_get_round. 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_get_round 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.
This server
Across the catalogue