AI agents call op_whoami to retrieve information from Op without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries authentication status and returns account information as a read-only operation. It has no side effects, cannot modify data, and provides only informational output about the current user context.
From the tool's definition Tool returns identity information ('currently authenticated 1Password account') without modifying any state. The verb 'Return' indicates retrieval only.
Attacks that exploit this kind of access
Return the currently authenticated 1Password account. It is categorised as a Read tool in the Op MCP Server, which means it retrieves data without modifying state.
Register the Op MCP server in PolicyLayer and add a rule for op_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 Op. Nothing to install.
op_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 op_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 op_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.
op_whoami is provided by the Op MCP server (jluckyiv/op-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 →