按主题查询本地整理的小程序官方文档、GitHub 项目和工程工具索引。
AI agents call miniapp_docs_lookup 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 searches through indexed documentation, GitHub project information, and engineering tool references. It has no capability to create, modify, delete, or execute code/commands. The operations are purely informational read-only queries against a local knowledge base. No side effects or state changes occur from using this tool.
From the tool's definition Tool performs document lookup and querying operations: '按主题查询本地整理的小程序官方文档、GitHub 项目和工程工具索引' (queries by topic local-organized official documents, GitHub projects, and engineering tool indexes).
Attacks that exploit this kind of access
按主题查询本地整理的小程序官方文档、GitHub 项目和工程工具索引。. 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_docs_lookup: 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_docs_lookup 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_docs_lookup 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_docs_lookup. 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_docs_lookup 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 →