Returns the current authentication state.
AI agents call auth.status to retrieve information from Tlc Portal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns authentication state information only. It performs no write operations, does not execute external commands, does not delete data, and does not involve financial transactions. The blast radius of misuse is minimal—an attacker learning authentication state cannot compromise the system directly through this tool alone. It is a straightforward Read operation.
From the tool's definition Tool name 'auth.status' and description 'Returns the current authentication state' indicate a query operation that retrieves current state without modification or side effects.
Attacks that exploit this kind of access
Returns the current authentication state. It is categorised as a Read tool in the Tlc Portal MCP Server, which means it retrieves data without modifying state.
Register the Tlc Portal MCP server in PolicyLayer and add a rule for 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 Tlc Portal. Nothing to install.
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 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 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.
auth.status is provided by the Tlc Portal MCP server (mingovvv/tlc-portal-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 →