atstake_legion_list_proposals
Every proposal in both legions, with tallies, rationales and the member roll,
This record as markdown: /tools/io-github-aibtcdev-mcp-server/atstake-legion-list-proposals.md
What atstake_legion_list_proposals does on Aibtc
AI agents call atstake_legion_list_proposals to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why atstake_legion_list_proposals is rated Low
Tool queries and lists proposal information without modifying data or triggering transactions.
From the tool's definition retrieves proposal data, tallies, rationales, member roll information
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs atstake_legion_list_proposals 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 atstake_legion_list_proposals, this is the rule to start with:
atstake_legion_list_proposals is read-only, so it stays allowed. 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 atstake_legion_list_proposals call is checked against it from then on.
Questions about atstake_legion_list_proposals
Every proposal in both legions, with tallies, rationales and the member roll,. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for atstake_legion_list_proposals: 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.
atstake_legion_list_proposals is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the atstake_legion_list_proposals 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 atstake_legion_list_proposals. 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.
atstake_legion_list_proposals 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