按关键词搜索文章标题和正文内容
AI agents call search_posts 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.
The search_posts tool queries and retrieves blog post data based on keyword criteria. It reads existing content without creating, modifying, deleting, or executing operations. This is a straightforward read operation with minimal security risk—the only concern would be exposure of sensitive information already stored in blog posts, but that is a data sensitivity issue rather than a capability risk.
From the tool's definition Tool name 'search_posts' and description '按关键词搜索文章标题和正文内容' (search articles by keywords in titles and body content) indicates a retrieval operation without modification or side effects.
Attacks that exploit this kind of access
按关键词搜索文章标题和正文内容. 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 search_posts: 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.
search_posts 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 search_posts 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 search_posts. 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.
search_posts 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 →