AI agents call konsulto_whoami to retrieve information from Konsulto 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 identity, permission, and context information about the current user and session. It performs no write, execution, deletion, or financial operations. The incomplete description ('and' with no trailing text) is minor and does not change the clear informational nature of the operation. Classification as Read is appropriate.
From the tool's definition Tool name 'konsulto_whoami' and description 'Show who the MCP is acting as, their permissions, the active audit' indicates a query/information retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Show who the MCP is acting as, their permissions, the active audit, and. It is categorised as a Read tool in the Konsulto MCP Server, which means it retrieves data without modifying state.
Register the Konsulto MCP server in PolicyLayer and add a rule for konsulto_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 Konsulto. Nothing to install.
konsulto_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 konsulto_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 konsulto_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.
konsulto_whoami is provided by the Konsulto MCP server (konsulto/konsulto-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 →