legion_vote
Vote yes or no with your current weight, with a written rationale recorded on chain.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/legion-vote.md
What legion_vote does on Aibtc
AI agents use legion_vote to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why legion_vote is rated Medium
An AI agent can call legion_vote faster than any human can review: one bad instruction and it creates or modifies resources in Aibtc by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs legion_vote 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_vote, this is the rule to start with:
legion_vote stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every legion_vote call is checked against it from then on.
Questions about legion_vote
Vote yes or no with your current weight, with a written rationale recorded on chain. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for legion_vote: 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_vote is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the legion_vote 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_vote. 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_vote 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.
This server
Across the catalogue