Read social posts from the BMAP API (query layer). Can fetch posts by author (BAP ID), specific post by transaction ID, or recent posts from all users. Supports pagination and feed functionality.
AI agents call bmap_readPosts 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.
This tool retrieves and queries existing social post data from the blockchain without creating, modifying, deleting, or executing any side effects. The pagination and feed functionality are standard query features. No financial transactions, code execution, or data mutations occur. The blast radius of misuse is minimal—an agent could only retrieve posts that are already publicly available on the blockchain.
From the tool's definition Tool name 'bmap_readPosts' and description explicitly states 'Read social posts from the BMAP API (query layer)' with capabilities to 'fetch posts by author', 'specific post by transaction ID', or 'recent posts'.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access bmap_readPosts 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 bmap_readPosts:
{
"version": "1",
"default": "deny",
"tools": {
"bmap_readPosts": {}
}
}bmap_readPosts 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.
Read social posts from the BMAP API (query layer). Can fetch posts by author (BAP ID), specific post by transaction ID, or recent posts from all users. Supports pagination and feed functionality. 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 bmap_readPosts: 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.
bmap_readPosts 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 bmap_readPosts 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 bmap_readPosts. 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.
bmap_readPosts 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.