输出 CloudBase MCP 与本地小程序工程顾问 MCP 的组合使用说明和安全边界。
AI agents call miniapp_cloudbase_mcp_guide to retrieve information from Wechat Miniapp Engineering without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays reference documentation—combination usage instructions and security boundaries. It has no side effects, does not modify data, execute code, or perform destructive operations. It is purely informational, making it a Read category tool with low severity.
From the tool's definition Tool description states it 'outputs' (输出) usage guidance and security boundaries for CloudBase MCP combined with the local mini-program engineering advisor MCP.
Attacks that exploit this kind of access
输出 CloudBase MCP 与本地小程序工程顾问 MCP 的组合使用说明和安全边界。. It is categorised as a Read tool in the Wechat Miniapp Engineering MCP Server, which means it retrieves data without modifying state.
Register the Wechat Miniapp Engineering MCP server in PolicyLayer and add a rule for miniapp_cloudbase_mcp_guide: 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 Wechat Miniapp Engineering. Nothing to install.
miniapp_cloudbase_mcp_guide is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the miniapp_cloudbase_mcp_guide 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.
Set action: deny in the PolicyLayer policy for miniapp_cloudbase_mcp_guide. 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.
miniapp_cloudbase_mcp_guide is provided by the Wechat Miniapp Engineering MCP server (lychee20000105/wechat-miniapp-engineering-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →