stop_preview · Hexo Blog MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_preview does on Hexo Blog MCP Server

AI agents invoke stop_preview 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.

WHY IT NEEDS A POLICY

Why stop_preview needs a policy

Stopping a running service is an Execute action - it triggers an external operation (terminating a process) whose effects depend on the current state of the system. While the blast radius is low (it only affects a local development preview and can be easily restarted), it is still an active operation rather than a read-only query or data modification.

From the tool's definition Tool description indicates it stops a running Hexo local preview server ('停止正在运行的 Hexo 本地预览服务器' = 'Stop the running Hexo local preview server'). This is a process/service termination action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_preview Rate-limited

stop_preview stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_preview": {
      "limits": [
        {
          "counter": "stop_preview_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Hexo Blog MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_preview

What does the stop_preview tool do? +

停止正在运行的 Hexo 本地预览服务器. 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.

How do I enforce a policy on stop_preview? +

Register the Hexo Blog MCP Server MCP server in PolicyLayer and add a rule for stop_preview: 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.

What risk level is stop_preview? +

stop_preview is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_preview? +

Yes. Add a rate_limit block to the stop_preview 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.

How do I block stop_preview completely? +

Set action: deny in the PolicyLayer policy for stop_preview. 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.

What MCP server provides stop_preview? +

stop_preview 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.