获取容器的日志输出
AI agents call get_container_logs to retrieve information from WeChat Official Account MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves log data from a container—a passive query operation with no side effects. While the server manages WeChat Official Accounts, this specific tool only fetches logs for inspection/monitoring purposes. No data is created, modified, deleted, or executed. The blast radius is minimal: logs may contain sensitive information but accessing them does not alter system state or trigger actions.
From the tool's definition Tool name 'get_container_logs' and description '获取容器的日志输出' (retrieve container log output) indicate a read-only operation that retrieves existing log data without modification or execution.
Attacks that exploit this kind of access
获取容器的日志输出. It is categorised as a Read tool in the WeChat Official Account MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WeChat Official Account MCP Server MCP server in PolicyLayer and add a rule for get_container_logs: 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 Official Account MCP Server. Nothing to install.
get_container_logs 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 get_container_logs 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 get_container_logs. 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.
get_container_logs is provided by the WeChat Official Account MCP Server MCP server (jungley8/mcp4agent). 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 →