pillar_position
View your Pillar wallet balance and Zest position.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/pillar-position.md
What pillar_position does on Aibtc
AI agents call pillar_position 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_position is rated Low
The verb 'View' and lack of any action verb (create, update, delete, execute) clearly indicate this is a read-only query operation. It retrieves wallet and position data but does not initiate transactions, transfers, or any state changes. While it accesses financial data (increasing concern slightly above generic reads), the tool itself performs no financial operations—it only displays information.
From the tool's definition Tool name 'pillar_position' and description 'View your Pillar wallet balance and Zest position' indicate retrieval of financial account information without modification.
Attacks that exploit this kind of access
The rule that runs pillar_position 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_position, this is the rule to start with:
pillar_position 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_position call is checked against it from then on.
Questions about pillar_position
View your Pillar wallet balance and Zest position. 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_position: 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_position 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_position 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_position. 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_position 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