AI agents use publish_post to create or update resources in Blogger — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blogger environment.
Publishing a post modifies data reversibly (the post can be unpublished or reverted), making this a Write operation rather than Execute or Destructive. The severity is medium because publishing can have reputational or content distribution consequences, but the action is reversible via the sibling 'revert_post' tool.
From the tool's definition Tool description states 'Publish a draft post' - this transitions a post from draft status to published status, modifying the post's state and making it visible to the public.
Attacks that exploit this kind of access
Publish a draft post. It is categorised as a Write tool in the Blogger MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blogger MCP server in PolicyLayer and add a rule for publish_post: 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 Blogger. Nothing to install.
publish_post 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 publish_post 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 publish_post. 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.
publish_post is provided by the Blogger MCP server (mech12/blogger-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 →