List all collectibles: Bitcoin inscriptions and Stacks NFTs.
AI agents call portfolio_get_collectibles to retrieve information from Bitcoin wallet MCP server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing collectibles (Bitcoin inscriptions and Stacks NFTs) without creating, modifying, deleting, or transferring assets. It is a read-only query operation with no side effects or blast radius if misused by an agent.
From the tool's definition Tool name contains 'get' and description states 'List all collectibles' — both indicate data retrieval with no modification or financial transaction.
Attacks that exploit this kind of access
List all collectibles: Bitcoin inscriptions and Stacks NFTs. 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 portfolio_get_collectibles: 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.
portfolio_get_collectibles 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 portfolio_get_collectibles 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 portfolio_get_collectibles. 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.
portfolio_get_collectibles 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →