创建一篇新的博客文章
AI agents use create_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.
The tool creates new blog post data, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. Severity is medium because an AI agent could create numerous unwanted posts or spam, but the impact is limited to blog content and is reversible via the delete_post tool.
From the tool's definition Tool name 'create_post' and description '创建一篇新的博客文章' (create a new blog post) indicates creation of new content. Server description confirms 'article CRUD operations' with Write capabilities.
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 create_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.
create_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 create_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 create_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.
create_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 →