修改指定文章的内容或元数据
AI agents use update_post to create or update resources in Hexo Blog MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hexo Blog MCP Server environment.
This tool creates or modifies blog post data reversibly. While it changes existing content, the operation is not inherently destructive—posts can be updated again or reverted via version control. The blast radius is medium because unintended modifications could corrupt blog content, but the effect is recoverable in a blogging platform context.
From the tool's definition Tool description states '修改指定文章的内容或元数据' (modify specified article content or metadata). The verb '修改' (modify/update) indicates reversible data modification. Tool name 'update_post' confirms write semantics.
Attacks that exploit this kind of access
修改指定文章的内容或元数据. It is categorised as a Write tool in the Hexo Blog MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hexo Blog 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 Hexo Blog 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 Hexo Blog MCP Server MCP server (leejersey/hexo-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 →