High Risk →

real_device_preview

Build and upload the game to WeChat for real device testing. Returns a QR code that the user can scan with WeChat. Requires AppID and upload private key (configurable via env vars or browser UI).

Part of the Weixin Minigame Helper MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke real_device_preview to trigger processes or run actions in Weixin Minigame Helper. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

real_device_preview can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

weixin-minigame-helper.yaml
tools:
  real_device_preview:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Weixin Minigame Helper policy for all 5 tools.

Tool Name real_device_preview
Category Execute
Risk Level High

Agents calling execute-class tools like real_device_preview have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

real_device_preview is one of the high-risk operations in Weixin Minigame Helper. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the real_device_preview tool do? +

Build and upload the game to WeChat for real device testing. Returns a QR code that the user can scan with WeChat. Requires AppID and upload private key (configurable via env vars or browser UI).. It is categorised as a Execute tool in the Weixin Minigame Helper MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on real_device_preview? +

Add a rule in your Intercept YAML policy under the tools section for real_device_preview. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Weixin Minigame Helper MCP server.

What risk level is real_device_preview? +

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

Can I rate-limit real_device_preview? +

Yes. Add a rate_limit block to the real_device_preview rule in your Intercept 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 real_device_preview completely? +

Set action: deny in the Intercept policy for real_device_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 real_device_preview? +

real_device_preview is provided by the Weixin Minigame Helper MCP server (@weadmin/weixin-minigame-helper-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Weixin Minigame Helper

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.