atstake_legion_status

Where a legion stands and whether you can act in it right now: your weight,

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/atstake-legion-status.md

WHAT IT DOES

What atstake_legion_status does on Aibtc

AI agents call atstake_legion_status 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.

RISK

Why atstake_legion_status is rated Low

Tool queries legion status and weight; retrieves data without side effects or modifications.

From the tool's definition Where a legion stands and whether you can act; your weight status.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs atstake_legion_status 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_status, this is the rule to start with:

atstake_legion_status Allowed

atstake_legion_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "atstake_legion_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every atstake_legion_status call is checked against it from then on.

FAQ

Questions about atstake_legion_status

What does the atstake_legion_status tool do? +

Where a legion stands and whether you can act in it right now: your weight,. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on atstake_legion_status? +

Register the Aibtc MCP server in PolicyLayer and add a rule for atstake_legion_status: 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.

What risk level is atstake_legion_status? +

atstake_legion_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit atstake_legion_status? +

Yes. Add a rate_limit block to the atstake_legion_status 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.

How do I block atstake_legion_status completely? +

Set action: deny in the PolicyLayer policy for atstake_legion_status. 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.

What MCP server provides atstake_legion_status? +

atstake_legion_status 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.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 366 Aibtc tools →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →