Update an existing draft
AI agents use substack_update_draft to create or update resources in Substack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Substack MCP Server environment.
This tool modifies existing draft content reversibly—updates can be undone by making further edits or discarding the draft before publication. It does not publish content (which would be Execute) or delete it (which would be Destructive). The medium severity reflects that an AI agent could maliciously modify a user's unpublished work, but the impact is limited to draft state and reversible before publication.
From the tool's definition Tool name 'substack_update_draft' and description 'Update an existing draft' indicate modification of existing data. Server description confirms 'creating drafts, publishing posts' as core capabilities.
Attacks that exploit this kind of access
Update an existing draft. It is categorised as a Write tool in the Substack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Substack MCP Server MCP server in PolicyLayer and add a rule for substack_update_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 MCP Server. Nothing to install.
substack_update_draft is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the substack_update_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 substack_update_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.
substack_update_draft is provided by the Substack MCP Server MCP server (jessicaruthabbott/my-substack-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 →