AI agents call check_wecom_auth to retrieve information from Wecom Doc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only validates the authentication state of stored credentials. It performs a read-only check that queries the validity of an existing cookie without creating, modifying, deleting, or executing any operations. The operation has no side effects and cannot damage or alter system state, making it a minimal-risk information retrieval action.
From the tool's definition Tool description '检查当前保存的 Cookie 是否仍然有效' (Check if currently saved Cookie is still valid) indicates a status check operation with no data retrieval, modification, or side effects.
Attacks that exploit this kind of access
检查当前保存的 Cookie 是否仍然有效. It is categorised as a Read tool in the Wecom Doc MCP Server, which means it retrieves data without modifying state.
Register the Wecom Doc MCP server in PolicyLayer and add a rule for check_wecom_auth: 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 Wecom Doc. Nothing to install.
check_wecom_auth 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 check_wecom_auth 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 check_wecom_auth. 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.
check_wecom_auth is provided by the Wecom Doc MCP server (tiansiyu-tj/wecom-doc-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 →