Publish a draft to your Substack
AI agents use substack_publish 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 creates new published content on the Substack platform, which is a reversible modification (posts can be unpublished or deleted). It does not permanently destroy data nor move money, so it falls under Write rather than Destructive or Financial. Severity is high because publishing can reach an audience immediately and unauthorized publication could damage reputation or expose sensitive information.
From the tool's definition Tool name 'substack_publish' and description 'Publish a draft to your Substack' indicate the tool creates/modifies published content by converting a draft into a live post.
Attacks that exploit this kind of access
Publish a draft to your Substack. 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_publish: 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_publish 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_publish 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_publish. 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_publish 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 →