Explore Bitcoin SV blockchain data using the WhatsOnChain API. Access multiple data types:\n\n
AI agents call bsv_explore to retrieve information from Bitcoin SV MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is designed to retrieve and explore blockchain data through an API, which is a pure read operation with no side effects, no code execution, and no ability to modify, delete, or move funds. The context of sibling tools (many performing reads like 'bmap_readFollows', 'bmap_readLikes', 'bmap_readPosts', 'bsocial_readPosts') confirms this is part of a read-focused data access layer.
From the tool's definition Tool name 'bsv_explore' and description 'Explore Bitcoin SV blockchain data using the WhatsOnChain API. Access multiple data types' indicate read-only querying of blockchain data with no modification capability.
Documented attack patterns abuse exactly the kind of access bsv_explore gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitcoin SV MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for bsv_explore:
{
"version": "1",
"default": "deny",
"tools": {
"bsv_explore": {}
}
} bsv_explore is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Explore Bitcoin SV blockchain data using the WhatsOnChain API. Access multiple data types:\n\n. It is categorised as a Read tool in the Bitcoin SV MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for bsv_explore: 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 SV MCP Server. Nothing to install.
bsv_explore 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 bsv_explore 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 bsv_explore. 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.
bsv_explore is provided by the Bitcoin SV MCP Server MCP server (b-open-io/bsv-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bitcoin SV MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
80 Bitcoin SV MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.