Get a full Substack post by slug. Returns title, author, date, and full article content. Source: getrecon.substack.com (36 posts on invariant testing, fuzzing, engagement retrospectives, product updates).
AI agents call get_substack_post to retrieve information from Recon Fuzz Knowledge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing published content from a Substack blog. There are no side effects, no data modification, no code execution, and no destructive operations. It is a straightforward read operation with minimal security risk—the worst case is an AI agent retrieving and summarizing blog posts.
From the tool's definition Tool retrieves full Substack post content by slug with read-only operation (get_substack_post). Description indicates it 'Returns title, author, date, and full article content' from a public Substack publication without modification, creation, or deletion…
Attacks that exploit this kind of access
Get a full Substack post by slug. Returns title, author, date, and full article content. Source: getrecon.substack.com (36 posts on invariant testing, fuzzing, engagement retrospectives, product updates). It is categorised as a Read tool in the Recon Fuzz Knowledge MCP Server, which means it retrieves data without modifying state.
Register the Recon Fuzz Knowledge MCP server in PolicyLayer and add a rule for get_substack_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 Recon Fuzz Knowledge. Nothing to install.
get_substack_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 get_substack_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 get_substack_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.
get_substack_post is provided by the Recon Fuzz Knowledge MCP server (recon-fuzz/recon-mcp-knowledge). 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 →