AI agents call get_session_status to retrieve information from Qldt Hanu without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current authentication status of the session. It performs a read-only query with no side effects, no code execution, no data modification, and no destructive operations. The low severity reflects minimal blast radius if misused—at worst, an agent learns whether authentication succeeded. The high confidence stems from clear, unambiguous language indicating a passive status check.
From the tool's definition Tool name 'get_session_status' and description 'Check if the server is authenticated' indicate a simple status check operation that queries authentication state without modifying, executing, or affecting data.
Attacks that exploit this kind of access
Check if the server is authenticated. It is categorised as a Read tool in the Qldt Hanu MCP Server, which means it retrieves data without modifying state.
Register the Qldt Hanu MCP server in PolicyLayer and add a rule for get_session_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 Qldt Hanu. Nothing to install.
get_session_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 get_session_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 get_session_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.
get_session_status is provided by the Qldt Hanu MCP server (qxbao/qldt-hanu-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 →