Get full details of a specific draft, including the body content.
AI agents call get_draft to retrieve information from Substack 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 draft information without any side effects. It performs a read-only operation on draft data. While the server as a whole includes destructive operations (delete_draft) and publishing operations, this specific tool only fetches data. No blast radius from accidental misuse beyond potential information disclosure of draft content the agent already has authorization to access.
From the tool's definition Tool name 'get_draft' and description 'Get full details of a specific draft, including the body content' indicate data retrieval with no modification or deletion.
Documented attack patterns abuse exactly the kind of access get_draft gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Substack, and nothing reaches the server without passing your rules. This is the rule we recommend for get_draft:
{
"version": "1",
"default": "deny",
"tools": {
"get_draft": {}
}
}get_draft 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.
Get full details of a specific draft, including the body content. It is categorised as a Read tool in the Substack MCP Server, which means it retrieves data without modifying state.
Register the Substack MCP server in PolicyLayer and add a rule for get_draft: 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. Nothing to install.
get_draft 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_draft 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_draft. 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_draft is provided by the Substack MCP server (nanameru/substack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Substack, 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.
11 Substack tools catalogued and risk-classified — across an index of 43,000+ MCP servers.