Post a short note (like a tweet)
AI agents use substack_post_note 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 content on Substack Notes (a public social feature) in a reversible manner—posted notes can be edited or deleted after publication. This is a Write operation (creates/modifies data reversibly) rather than Execute or Destructive, as it doesn't run arbitrary code or permanently delete content.
From the tool's definition Tool description states it will 'Post a short note', and the server description indicates it 'support[s] specialized features like...posting to Substack Notes'.
Attacks that exploit this kind of access
Post a short note (like a tweet). 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_post_note: 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_post_note 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_post_note 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_post_note. 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_post_note 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 →