legion_sponsor
Fund the pool WITHOUT minting voting weight, with a name on the record.\n\n
This record as markdown: /tools/io-github-aibtcdev-mcp-server/legion-sponsor.md
What legion_sponsor does on Aibtc
AI agents use legion_sponsor to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why legion_sponsor is rated Critical
The tool moves funds ('Fund the pool') into a pool, which constitutes a financial commitment. Even though it doesn't mint voting weight, it still transfers/commits financial resources to a pool. The presence of other financial tools (alex_swap, bitflow_create_order) on the same server reinforces this classification.
From the tool's definition Fund the pool WITHOUT minting voting weight, with a name on the record
Attacks that exploit this kind of access
The rule that runs legion_sponsor 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 legion_sponsor, this is the rule to start with:
Any call to legion_sponsor 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 legion_sponsor call is checked against it from then on.
Questions about legion_sponsor
Fund the pool WITHOUT minting voting weight, with a name on the record.\n\n. 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 legion_sponsor: 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.
legion_sponsor 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 legion_sponsor 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 legion_sponsor. 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.
legion_sponsor 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