pillar_key_info

Show signing key info: pubkey, smart wallet, lock status, and all stored keys.

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/pillar-key-info.md

WHAT IT DOES

What pillar_key_info does on Aibtc

AI agents call pillar_key_info 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 pillar_key_info is rated Low

This tool retrieves and displays information about signing keys and wallet status. It performs no writes, deletions, code execution, or financial transactions. The action is read-only and informational, making it a Read category tool with low severity since exposure of this information to an AI agent would not directly cause harm beyond potential information disclosure.

From the tool's definition Tool description states 'Show signing key info: pubkey, smart wallet, lock status, and all stored keys' — purely informational retrieval with no modifications, deletions, or external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pillar_key_info Allowed

pillar_key_info 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": {
    "pillar_key_info": {}
  }
}

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 pillar_key_info call is checked against it from then on.

FAQ

Questions about pillar_key_info

What does the pillar_key_info tool do? +

Show signing key info: pubkey, smart wallet, lock status, and all stored keys. 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 pillar_key_info? +

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

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

Can I rate-limit pillar_key_info? +

Yes. Add a rate_limit block to the pillar_key_info 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 pillar_key_info completely? +

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

pillar_key_info 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 358 Aibtc tools →

Across the catalogue

get_team_info on CTFtime MCP Server → The MCP Attack Database →

Guides

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