AI agents call check_auth_status to retrieve information from Juejin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Checking authorization status is a pure information retrieval operation that queries the current state without modifying, executing external operations, deleting data, or committing financial actions. It belongs in the Read category. Severity is low because even if misused by an AI agent, learning the auth status poses minimal risk—no data is modified, no code is executed, and no irreversible actions are triggered.
From the tool's definition Tool name and description indicate 'check_auth_status' (检查授权状态 = check authorization status) performs a status check/query operation to verify current authentication or authorization state. This is a read-only operation with no side effects.
Attacks that exploit this kind of access
检查授权状态. It is categorised as a Read tool in the Juejin MCP Server, which means it retrieves data without modifying state.
Register the Juejin MCP server in PolicyLayer and add a rule for check_auth_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 Juejin. Nothing to install.
check_auth_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 check_auth_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 check_auth_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.
check_auth_status is provided by the Juejin MCP server (ztxtxwd/juejin-mcp-server). 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 →