读取 MCP 优化日志，默认返回最近 10 条 Markdown 记录。
AI agents call local_mcp_read_optimization_log 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 only retrieves and queries existing optimization log data with no side effects. It performs a read-only operation that retrieves historical log entries. There is no modification, deletion, execution of arbitrary code, or financial impact. This is a straightforward data retrieval operation.
From the tool's definition Tool name contains 'read' and description states '读取 MCP 优化日志' (read MCP optimization logs), with a default return of the 10 most recent Markdown records.
Attacks that exploit this kind of access
读取 MCP 优化日志，默认返回最近 10 条 Markdown 记录。. 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_mcp_read_optimization_log: 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_mcp_read_optimization_log 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_mcp_read_optimization_log 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_mcp_read_optimization_log. 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_mcp_read_optimization_log 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 →