AI agents call lexq_whoami to retrieve information from LexQ without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays authentication context information. It performs no mutations, does not execute external operations, and does not access sensitive business data—only displays masked/safe authentication metadata. Typical for identity verification in API contexts. Categorized as Read with low severity since misuse would only expose the user's own authentication context, not enable unauthorized actions.
From the tool's definition Tool name 'lexq_whoami' and description 'Show current authentication info (tenant name, role, API key mask)' indicates retrieval of authentication metadata only. Returns read-only information about the authenticated user without modifying state.
Attacks that exploit this kind of access
Show current authentication info (tenant name, role, API key mask). It is categorised as a Read tool in the LexQ MCP Server, which means it retrieves data without modifying state.
Register the LexQ MCP server in PolicyLayer and add a rule for lexq_whoami: 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 LexQ. Nothing to install.
lexq_whoami 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 lexq_whoami 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 lexq_whoami. 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.
lexq_whoami is provided by the LexQ MCP server (lexq-io/lexq-cli). 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 →