把功能拆成需求、UI、前端、后端、测试、上线六类任务清单。
AI agents call miniapp_work_breakdown 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 is a planning and documentation tool that analyzes features and generates structured task breakdowns. It retrieves or transforms information about project structure without creating, modifying, executing, or deleting anything. The output is a task list/blueprint for human consumption, making it a Read operation with minimal blast radius if misused.
From the tool's definition Tool description indicates it breaks down features into task categories (requirements, UI, frontend, backend, testing, deployment) - a decomposition/analysis function.
Attacks that exploit this kind of access
把功能拆成需求、UI、前端、后端、测试、上线六类任务清单。. 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_work_breakdown: 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_work_breakdown 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_work_breakdown 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_work_breakdown. 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_work_breakdown 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 →