Claim winnings from resolved market.
AI agents use redeem_winnings to commit financial operations through Basis MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Redeeming winnings initiates a financial transaction that transfers cryptocurrency from a smart contract to a user's wallet. This constitutes a financial operation with high blast radius if misused, as it interacts with on-chain funds in a prediction market context.
From the tool's definition 'Claim winnings from resolved market' — this tool moves funds (winnings) to the caller from a prediction market contract on BNB Smart Chain.
Attacks that exploit this kind of access
Claim winnings from resolved market. 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 redeem_winnings: 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.
redeem_winnings 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 redeem_winnings 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 redeem_winnings. 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.
redeem_winnings 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 →