bsocial_readPosts
Read social posts from the BSV blockchain using BMAP API. Can fetch posts by author (BAP ID), specific post by transaction ID, or recent posts from all users. Supports pagination and feed functionality.
This record as markdown: /tools/b-open-io-bsv-mcp/bsocial-readposts.md
What bsocial_readPosts does on Bitcoin SV MCP Server
AI agents call bsocial_readPosts to retrieve information from Bitcoin SV 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 bsocial_readPosts is rated Low
This tool retrieves and queries social post data from the blockchain without any side effects. It performs data retrieval operations (fetch, read) across multiple query patterns but does not create, modify, delete, or execute any operations. The capability to paginate and filter results does not change its fundamental read-only nature. This is a straightforward Read category tool with low risk of misuse.
From the tool's definition Tool name is 'bsocial_readPosts' and description states it 'Read social posts from the BSV blockchain' with operations to 'fetch posts by author', 'specific post by transaction ID', or 'recent posts' with 'pagination and feed functionality'.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bsocial_readPosts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bitcoin SV MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bsocial_readPosts, this is the rule to start with:
bsocial_readPosts 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 SV MCP Server, apply this rule, and every bsocial_readPosts call is checked against it from then on.
Questions about bsocial_readPosts
Read social posts from the BSV blockchain using BMAP API. 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 bsocial_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.
bsocial_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 bsocial_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 bsocial_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.
bsocial_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.
More on Bitcoin SV MCP Server, and thousands of servers like it.
This server
Across the catalogue