Append content to an existing draft (for live blogging)
AI agents use substack_append_to_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 data (draft posts) by appending content, which is characteristic of Write category operations. It is reversible—appended content can be edited or removed.
From the tool's definition Tool appends content to an existing draft, a reversible modification operation. Description explicitly states it's used for 'live blogging,' indicating dynamic content updates to draft posts.
Attacks that exploit this kind of access
Append content to an existing draft (for live blogging). 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_append_to_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_append_to_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_append_to_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_append_to_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_append_to_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 →