Read the full content of a specific post (draft or published) with all its formatting. Returns the post in a readable markdown format. Useful for reviewing content, copying from old posts, or checking formatting.
AI agents call get_post_content to retrieve information from Substack Mcp Plus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries existing post data without creating, modifying, deleting, or executing any operations. It has no side effects and presents minimal risk—the worst-case scenario is exposure of post content the caller already has access to.
From the tool's definition Tool description explicitly states 'Read the full content' and 'Returns the post in a readable markdown format.' The use cases listed are review-oriented: 'reviewing content, copying from old posts, or checking formatting.' No modifications or state changes…
Documented attack patterns abuse exactly the kind of access get_post_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Substack Mcp Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for get_post_content:
{
"version": "1",
"default": "deny",
"tools": {
"get_post_content": {}
}
}get_post_content 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 the full content of a specific post (draft or published) with all its formatting. Returns the post in a readable markdown format. Useful for reviewing content, copying from old posts, or checking formatting. It is categorised as a Read tool in the Substack Mcp Plus MCP Server, which means it retrieves data without modifying state.
Register the Substack Mcp Plus MCP server in PolicyLayer and add a rule for get_post_content: 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 Mcp Plus. Nothing to install.
get_post_content 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 get_post_content 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 get_post_content. 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.
get_post_content is provided by the Substack Mcp Plus MCP server (ty13r/substack-mcp-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Substack Mcp Plus, 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.
12 Substack Mcp Plus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.