get_wallet_info

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

WHAT IT DOES

What get_wallet_info does on Aibtc

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

The tool name suggests it retrieves wallet information, and the verb 'Get' is consistent with Read category operations. The truncated description 'Get the agent' is uninformative but does not suggest side effects. Given the context of other tools on the server (swap, create_order, list operations), this appears to be a query/retrieval function.

From the tool's definition Tool name 'get_wallet_info' 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 get_wallet_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 get_wallet_info, this is the rule to start with:

get_wallet_info Allowed

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

FAQ

Questions about get_wallet_info

What does the get_wallet_info 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 get_wallet_info? +

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

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

Can I rate-limit get_wallet_info? +

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

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

get_wallet_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 →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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