Read likes and reactions for a specific post from the BMAP API. Shows who liked the post and what emoji reactions were used.
AI agents call bmap_readLikes 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 displays existing data (likes/reactions) from a blockchain social protocol without creating, modifying, deleting, or executing any state-changing operations. It is a pure read operation on public blockchain data, presenting minimal security risk.
From the tool's definition Tool name 'bmap_readLikes' and description explicitly states 'Read likes and reactions for a specific post' — a retrieval operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access bmap_readLikes 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_readLikes:
{
"version": "1",
"default": "deny",
"tools": {
"bmap_readLikes": {}
}
} bmap_readLikes 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 likes and reactions for a specific post from the BMAP API. Shows who liked the post and what emoji reactions were used. 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_readLikes: 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_readLikes 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_readLikes 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_readLikes. 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_readLikes 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.