读取指定文章的完整内容（含 Front-matter 和正文）
AI agents call read_post to retrieve information from Hexo Blog MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves article content including metadata (Front-matter) and body text. It is a query operation that has no side effects—it neither modifies, deletes, nor executes code. The read-only nature and lack of destructive or write capabilities place it firmly in the Read category with low severity.
From the tool's definition Tool name is 'read_post' and description states it reads complete content of a specified article. The verb '读取' (read/fetch) indicates data retrieval with no modifications.
Attacks that exploit this kind of access
读取指定文章的完整内容（含 Front-matter 和正文）. It is categorised as a Read tool in the Hexo Blog MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hexo Blog MCP Server MCP server in PolicyLayer and add a rule for read_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.
read_post is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_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 read_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.
read_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 →