读取本地规则后提炼的工作画像，包括沟通、交付、安全、知识库和编码习惯。
AI agents call local_user_profile 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 performs data retrieval and analysis of locally stored profile information. It extracts and presents existing data about user work patterns without creating, modifying, deleting, or executing any operations. The blast radius of misuse is limited to potential exposure of user work profile information, which would be a confidentiality concern but not a functional risk to systems or data integrity.
From the tool's definition Tool name contains 'read' (读取) and description states it 'reads local rules and extracts work profile' (读取本地规则后提炼的工作画像).
Attacks that exploit this kind of access
读取本地规则后提炼的工作画像，包括沟通、交付、安全、知识库和编码习惯。. 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 local_user_profile: 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.
local_user_profile 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 local_user_profile 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 local_user_profile. 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.
local_user_profile 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 →