检查当前 PingCode 登录状态。
AI agents call check_auth to retrieve information from PingCode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only status check of the user's authentication state. It has no side effects, does not modify data, does not execute code or commands, and does not delete or move resources. It is a simple informational query, making it a Read category tool with low severity since misuse would only reveal authentication status without causing operational harm.
From the tool's definition Tool name 'check_auth' and description '检查当前 PingCode 登录状态' (Check current PingCode login status) indicate a query operation that retrieves authentication state information without modifying, executing external actions, or affecting data.
Attacks that exploit this kind of access
检查当前 PingCode 登录状态。. It is categorised as a Read tool in the PingCode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PingCode MCP Server MCP server in PolicyLayer and add a rule for check_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 PingCode MCP Server. Nothing to install.
check_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_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_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_auth is provided by the PingCode MCP Server MCP server (ratatatat1/pingcode-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 →