logi_whoami
Use when the user asks 'am I logged in?', 'which logi account is this?', or whenever you need to verify the configured PAK is valid before another tool call. Read-only. Returns the email + scopes of the current PAK. Do NOT use to list login history — use logi_list_login_history.
This record as markdown: /tools/1pass-mcp/logi-whoami.md
What logi_whoami does on 1pass
AI agents call logi_whoami to retrieve information from 1pass without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why logi_whoami is rated Low
Even though logi_whoami only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs logi_whoami safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1pass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For logi_whoami, this is the rule to start with:
logi_whoami is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 1pass, apply this rule, and every logi_whoami call is checked against it from then on.
Questions about logi_whoami
Use when the user asks 'am I logged in?', 'which logi account is this?', or whenever you need to verify the configured PAK is valid before another tool call. Read-only. Returns the email + scopes of the current PAK. Do NOT use to list login history — use logi_list_login_history. It is categorised as a Read tool in the 1pass MCP Server, which means it retrieves data without modifying state.
Register the 1pass MCP server in PolicyLayer and add a rule for logi_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 1pass. Nothing to install.
logi_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 logi_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 logi_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.
logi_whoami is provided by the 1pass MCP server (@1pass/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1pass, and thousands of servers like it.
This server
Across the catalogue