xhs_generate_cover · XHS- MCP: Risk & Policy

WHAT IT DOES

What xhs_generate_cover does on XHS-MCP

AI agents invoke xhs_generate_cover to trigger actions in XHS-MCP. 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 xhs_generate_cover needs a policy

This tool triggers an external operation (image generation) based on input arguments. It is not a simple read/write of existing data, but rather executes a generation process. It could also be considered Write since it creates an image artifact, but the generative/computational execution aspect and its dependency on external browser automation make Execute the most appropriate category.

From the tool's definition 为指定的笔记生成发布需要的封面图片 — generates cover images required for publishing a note, triggering an external image generation operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

xhs_generate_cover Rate-limited

xhs_generate_cover 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": {
    "xhs_generate_cover": {
      "limits": [
        {
          "counter": "xhs_generate_cover_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 XHS-MCP, so you can run agents against it safely.

FAQ

Questions about xhs_generate_cover

What does the xhs_generate_cover tool do? +

为指定的笔记生成发布需要的封面图片. It is categorised as a Execute tool in the XHS-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on xhs_generate_cover? +

Register the XHS- MCP server in PolicyLayer and add a rule for xhs_generate_cover: 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 XHS-MCP. Nothing to install.

What risk level is xhs_generate_cover? +

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

Can I rate-limit xhs_generate_cover? +

Yes. Add a rate_limit block to the xhs_generate_cover 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 xhs_generate_cover completely? +

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

xhs_generate_cover is provided by the XHS- MCP server (lastkimi/xhs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.