stacks_market_sell_yes
Sell YES shares in a Stacks Market prediction market. Uses the sell-yes-auto function with a minimum proceeds guard. The transaction will fail if proceeds fall below min_proceeds_ustx. Requires an unlocked wallet. Only available on mainnet.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/stacks-market-sell-yes.md
What stacks_market_sell_yes does on Aibtc
AI agents use stacks_market_sell_yes to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why stacks_market_sell_yes is rated Critical
This tool executes a real financial transaction on mainnet — selling prediction market shares and receiving STX proceeds. It directly moves/commits financial value on a live blockchain, making it Financial category. The critical severity reflects that it operates on mainnet with an unlocked wallet, meaning misuse could result in irreversible loss of funds.
From the tool's definition Sell YES shares in a Stacks Market prediction market... Uses the sell-yes-auto function with a minimum proceeds guard... Requires an unlocked wallet. Only available on mainnet.
Attacks that exploit this kind of access
The rule that runs stacks_market_sell_yes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stacks_market_sell_yes, this is the rule to start with:
Any call to stacks_market_sell_yes is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every stacks_market_sell_yes call is checked against it from then on.
Questions about stacks_market_sell_yes
Sell YES shares in a Stacks Market prediction market. Uses the sell-yes-auto function with a minimum proceeds guard. The transaction will fail if proceeds fall below min_proceeds_ustx. Requires an unlocked wallet. Only available on mainnet. It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for stacks_market_sell_yes: 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 Aibtc. Nothing to install.
stacks_market_sell_yes 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 stacks_market_sell_yes 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 stacks_market_sell_yes. 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.
stacks_market_sell_yes is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
Across the catalogue