Check current TreeBeam authentication status — whether a valid token is stored and when it expires. If the user is not authenticated, log them in with the treebeam_login tool before using other tools that would require authentication.
AI agents call treebeam_auth_status to retrieve information from TreeBeam MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only check of authentication state. It does not create, modify, delete, or execute any operations; it merely returns status information about token validity and expiration. This is a non-destructive information retrieval operation, classifying it as Read with low severity since compromise would only expose auth metadata, not trigger financial or data-modifying actions.
From the tool's definition Tool description states it 'Check[s] current TreeBeam authentication status — whether a valid token is stored and when it expires.' This is a query operation that retrieves authentication metadata with no side effects.
Attacks that exploit this kind of access
Check current TreeBeam authentication status — whether a valid token is stored and when it expires. If the user is not authenticated, log them in with the treebeam_login tool before using other tools that would require authentication. It is categorised as a Read tool in the TreeBeam MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TreeBeam MCP Server MCP server in PolicyLayer and add a rule for treebeam_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 TreeBeam MCP Server. Nothing to install.
treebeam_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 treebeam_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 treebeam_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.
treebeam_auth_status is provided by the TreeBeam MCP Server MCP server (treebeam-code/tb-mcpserver). 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 →