wallet_get_supported_methods
List all available MCP tools with their names and descriptions.
This record as markdown: /tools/markmhendrickson-mcp-server-bitcoin/wallet-get-supported-methods.md
What wallet_get_supported_methods does on Bitcoin wallet MCP server
AI agents call wallet_get_supported_methods to retrieve information from Bitcoin wallet MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wallet_get_supported_methods is rated Low
This tool retrieves and displays information about available methods—a non-destructive query operation. It has no side effects, does not move funds, execute code, or modify data. While the server provides financial operations (sending Bitcoin), this specific tool is purely informational.
From the tool's definition Tool name 'wallet_get_supported_methods' and description 'List all available MCP tools with their names and descriptions' indicate a read-only operation that retrieves metadata about available tools without modifying state or executing operations.
Attacks that exploit this kind of access
The rule that runs wallet_get_supported_methods safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bitcoin wallet MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wallet_get_supported_methods, this is the rule to start with:
wallet_get_supported_methods 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 Bitcoin wallet MCP server, apply this rule, and every wallet_get_supported_methods call is checked against it from then on.
Questions about wallet_get_supported_methods
List all available MCP tools with their names and descriptions. It is categorised as a Read tool in the Bitcoin wallet MCP server MCP Server, which means it retrieves data without modifying state.
Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for wallet_get_supported_methods: 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 Bitcoin wallet MCP server. Nothing to install.
wallet_get_supported_methods 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 wallet_get_supported_methods 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 wallet_get_supported_methods. 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.
wallet_get_supported_methods is provided by the Bitcoin wallet MCP server MCP server (markmhendrickson/mcp-server-bitcoin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bitcoin wallet MCP server, and thousands of servers like it.
This server
Across the catalogue