check_login_status
AI agents call check_login_status to retrieve information from YST KPI Daily Report Collector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool checks an existing login status without modifying data, creating resources, executing arbitrary code, or causing destructive changes. This is a read-only query operation. Severity is low because it retrieves only authentication metadata with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'check_login_status' and server context indicate this tool queries the current authentication state of a browser session. No side effects or mutations are implied.
Attacks that exploit this kind of access
check_login_status. It is categorised as a Read tool in the YST KPI Daily Report Collector MCP Server, which means it retrieves data without modifying state.
Register the YST KPI Daily Report Collector MCP server in PolicyLayer and add a rule for check_login_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 YST KPI Daily Report Collector. Nothing to install.
check_login_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_login_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_login_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_login_status is provided by the YST KPI Daily Report Collector MCP server (xuzan9396/yst_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 →