This record as markdown: /tools/io-github-aibtcdev-mcp-server/pillar-status.md
What pillar_status does on Aibtc
AI agents call pillar_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.
Why pillar_status is rated Low
Status checks are typically read operations that retrieve information without modifying state. However, confidence is reduced due to the truncated/incomplete description, which makes full intent unclear. The presence of financial tools (swap, create_order) on the same server suggests this may relate to financial queries, but 'status' implies passive retrieval rather than transactional behavior.
From the tool's definition Tool name 'pillar_status' and description prefix 'Check if you' suggests a status check or query operation. The incomplete description ('Check if you') is uninformative, but the naming pattern aligns with read-only operations.
Attacks that exploit this kind of access
The rule that runs pillar_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 pillar_status, this is the rule to start with:
pillar_status 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 pillar_status call is checked against it from then on.
Questions about pillar_status
Check if you. 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 pillar_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.
pillar_status 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 pillar_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.
Set action: deny in the PolicyLayer policy for pillar_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.
pillar_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.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue