Read the full content of a Substack post
AI agents call read_post to retrieve information from Substack Reader 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 Substack post content. It has no side effects—it does not create, modify, delete, or execute anything. It is a straightforward read operation that queries data the user is already subscribed to or has access to. The blast radius of misuse is minimal; an agent could only retrieve content the authenticated user can already access.
From the tool's definition Tool name is 'read_post' and description states 'Read the full content of a Substack post'. The action is explicitly retrieval of content with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Read the full content of a Substack post. It is categorised as a Read tool in the Substack Reader MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Substack Reader MCP Server MCP server in PolicyLayer and add a rule for read_post: 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 Substack Reader MCP Server. Nothing to install.
read_post 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 read_post 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 read_post. 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.
read_post is provided by the Substack Reader MCP Server MCP server (kealu-inc/substack-reader-mcp). 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 →