wake_display · xigua- MCP: Risk & Policy

WHAT IT DOES

What wake_display does on xigua-MCP

AI agents invoke wake_display to trigger actions in xigua-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 wake_display needs a policy

This tool executes a system-level operation to wake the display on Windows. It doesn't read, write, or delete data, nor does it involve financial transactions. It's an OS/hardware control action with minimal blast radius — the worst case is unexpectedly waking a display, which is easily reversible.

From the tool's definition 唤醒被关闭的显示器（仅Windows） — triggers an external hardware/OS operation (waking the display)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wake_display Rate-limited

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

FAQ

Questions about wake_display

What does the wake_display tool do? +

唤醒被关闭的显示器（仅Windows）. It is categorised as a Execute tool in the xigua-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 wake_display? +

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

What risk level is wake_display? +

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

Can I rate-limit wake_display? +

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

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

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