wallet_status

Get the agent

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/wallet-status.md

WHAT IT DOES

What wallet_status does on Aibtc

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

The tool appears to query wallet or agent status without creating, modifying, deleting, or executing code. The description is minimal ('Get the agent'), but the name and context suggest read-only retrieval. Confidence is moderate rather than high due to the vague description, but no evidence of side effects is present.

From the tool's definition Tool name 'wallet_status' and description 'Get the agent' indicate a retrieval operation with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wallet_status Allowed

wallet_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": {
    "wallet_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 wallet_status call is checked against it from then on.

FAQ

Questions about wallet_status

What does the wallet_status tool do? +

Get the agent. 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 wallet_status? +

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

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

Can I rate-limit wallet_status? +

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

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

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

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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