Aggregate UPDOWN bet/claim summary for your wallet across every asset (BTC/ETH/BNB/CAKE/DOGE) and all timeframes — totals, win/loss tallies, and embedded activeBets[] / claimableBets[] arrays.
AI agents call updown_my_history to retrieve information from Basis MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval and aggregation operations with no side effects. It assembles a summary view of historical betting activity and claimable positions, but does not create, modify, delete, or execute any financial transactions. The 'history' and 'summary' framing confirms a read-only query operation.
From the tool's definition Tool retrieves and aggregates historical bet data and summary statistics ('Aggregate UPDOWN bet/claim summary', 'totals, win/loss tallies', 'activeBets[] / claimableBets[] arrays') without modifying, deleting, or executing transactions.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Aggregate UPDOWN bet/claim summary for your wallet across every asset (BTC/ETH/BNB/CAKE/DOGE) and all timeframes — totals, win/loss tallies, and embedded activeBets[] / claimableBets[] arrays. 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_my_history: 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_my_history 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_my_history 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_my_history. 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_my_history 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →