debug_publish_content · Xhs Kit MCP: Risk & Policy

WHAT IT DOES

What debug_publish_content does on Xhs Kit

AI agents use debug_publish_content to create or update resources in Xhs Kit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xhs Kit environment.

WHY IT NEEDS A POLICY

Why debug_publish_content needs a policy

Although framed as a debug/validation tool that does not actually publish, it is intrinsically linked to the publish_content operation and interacts with content creation systems. The tool performs verification of publishing workflows, which is a Write operation (content modification/creation pathway). However, because it operates in debug mode and does not actually publish, the severity is medium rather than high.

From the tool's definition Tool description states 'Debug 模式：验证发布内容而不实际发布' (Debug mode: verify publishing content without actually publishing). The tool name is 'debug_publish_content' and description explicitly mentions content validation in a debug context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

debug_publish_content Rate-limited

debug_publish_content stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "debug_publish_content": {
      "limits": [
        {
          "counter": "debug_publish_content_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 Kit, so you can run agents against it safely.

FAQ

Questions about debug_publish_content

What does the debug_publish_content tool do? +

Debug 模式：验证发布内容而不实际发布. It is categorised as a Write tool in the Xhs Kit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on debug_publish_content? +

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

What risk level is debug_publish_content? +

debug_publish_content is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit debug_publish_content? +

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

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

debug_publish_content is provided by the Xhs Kit MCP server (luweizheng/xhs-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.