Met à jour un post existant
AI agents use update_post to create or update resources in Blogger MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blogger MCP Server environment.
The tool modifies blog post content reversibly. It is a Write operation rather than Destructive because updates do not irreversibly erase data—they change it, and prior versions may be recoverable or the change can be undone through subsequent updates. The medium severity reflects that a compromised agent could alter published content, affecting blog integrity and reader trust, but the operation is not irreversible.
From the tool's definition Tool name 'update_post' and description 'Met à jour un post existant' (updates an existing post) indicates modification of existing data without permanent deletion.
Attacks that exploit this kind of access
Met à jour un post existant. It is categorised as a Write tool in the Blogger MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blogger MCP Server MCP server in PolicyLayer and add a rule for update_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 MCP Server. Nothing to install.
update_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 update_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 update_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.
update_post is provided by the Blogger MCP Server MCP server (niyonabil/blogger-mcp-server). 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 →