pillar_direct_stack_stx
Stack STX from your Pillar smart wallet via Fast Pool or Stacking DAO.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/pillar-direct-stack-stx.md
What pillar_direct_stack_stx does on Aibtc
AI agents use pillar_direct_stack_stx to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why pillar_direct_stack_stx is rated Critical
This tool moves/commits STX cryptocurrency tokens from a user's smart wallet into a stacking pool, which is a financial operation involving real assets. Misuse could result in unintended locking of funds in stacking contracts, constituting a significant financial risk.
From the tool's definition Stack STX from your Pillar smart wallet via Fast Pool or Stacking DAO
Attacks that exploit this kind of access
The rule that runs pillar_direct_stack_stx 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 pillar_direct_stack_stx, this is the rule to start with:
Any call to pillar_direct_stack_stx 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 pillar_direct_stack_stx call is checked against it from then on.
Questions about pillar_direct_stack_stx
Stack STX from your Pillar smart wallet via Fast Pool or Stacking DAO. 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 pillar_direct_stack_stx: 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.
pillar_direct_stack_stx 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 pillar_direct_stack_stx 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 pillar_direct_stack_stx. 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.
pillar_direct_stack_stx 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