启动 Hexo 本地预览服务器(localhost:4000)
AI agents invoke preview_blog to trigger actions in Hexo Blog MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool launches a local server process (Hexo dev server on port 4000), which is an external operation/execution. It doesn't just read data — it starts a running service. This fits Execute, not Read. Misuse could tie up ports or expose local content, giving it medium severity.
From the tool's definition 启动 Hexo 本地预览服务器(localhost:4000)— 'starts' a local preview server, triggering an external process/service
Attacks that exploit this kind of access
启动 Hexo 本地预览服务器(localhost:4000). It is categorised as a Execute tool in the Hexo Blog MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hexo Blog MCP Server MCP server in PolicyLayer and add a rule for preview_blog: 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.
preview_blog is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the preview_blog 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 preview_blog. 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.
preview_blog 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 →