查看 MCP 优化日志状态、路径、记录数和强制记录规则。
AI agents call local_mcp_optimization_log_status 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 status information about optimization logs, including metadata like path, record count, and configuration rules. It performs only read operations with no side effects, making it a Read category tool with low severity risk.
From the tool's definition Tool name contains '查看' (view/check) and description states it checks 'MCP optimization log status, path, record count, and force logging rules' — purely informational operations with no modification or execution capability.
Attacks that exploit this kind of access
查看 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 local_mcp_optimization_log_status: 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_optimization_log_status 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_optimization_log_status 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_optimization_log_status. 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_optimization_log_status 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 →