Check the current API key owner and permissions.
AI agents call whoami to retrieve information from Otoinstall without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about the authenticated user and their access level but does not modify, execute operations, or affect system state. The use of 'Check' and the informational nature of the request place it squarely in the Read category. Severity is low because misuse would only expose identity information already associated with the API key in use.
From the tool's definition Tool name 'whoami' and description 'Check the current API key owner and permissions' indicate a read-only query of identity and permission information with no side effects.
Attacks that exploit this kind of access
Check the current API key owner and permissions. It is categorised as a Read tool in the Otoinstall MCP Server, which means it retrieves data without modifying state.
Register the Otoinstall MCP server in PolicyLayer and add a rule for 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 Otoinstall. Nothing to install.
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 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 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.
whoami is provided by the Otoinstall MCP server (otoinstall-mcp-server). 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 →