Tenancy/user/region from loaded OCI config — canonical 'connected?' check.
AI agents call whoami to retrieve information from OCI MCP Server 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 identity and authentication context information without modifying, deleting, executing code, or initiating any transactions. It is a diagnostic read operation typical of credential and connection verification. The low severity reflects minimal blast radius—misuse only reveals authenticated identity information already available to the connected client.
From the tool's definition Tool name is 'whoami' and description states it 'returns Tenancy/user/region from loaded OCI config' with purpose as a 'canonical connected? check'. This is purely informational retrieval with no side effects.
Attacks that exploit this kind of access
Tenancy/user/region from loaded OCI config — canonical 'connected?' check. It is categorised as a Read tool in the OCI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OCI MCP Server 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 OCI MCP Server. 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 OCI MCP Server MCP server (sarthak-pansare/oci-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 →