logi_list_login_history

Use when the user asks about recent sign-ins, suspicious access, login locations, or wants to audit account activity. Read-only. Returns the latest N (default 30, max 100) login events with country, IP, and a suspicious flag. Each row carries an id you can pass to logi_delete_login_log.

SERVER1pass SOURCE@1pass/mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1pass-mcp/logi-list-login-history.md

WHAT IT DOES

What logi_list_login_history does on 1pass

AI agents call logi_list_login_history 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.

Parameter	Type	Required	Description
`limit`	number	—

Parameters from the server's own tool schema.

RISK

Why logi_list_login_history is rated Low

Even though logi_list_login_history 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

RECOMMENDED RULE

The rule that runs logi_list_login_history 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_list_login_history, this is the rule to start with:

logi_list_login_history Allowed

logi_list_login_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "logi_list_login_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 1pass, apply this rule, and every logi_list_login_history call is checked against it from then on.

FAQ

Questions about logi_list_login_history

What does the logi_list_login_history tool do? +

What parameters does logi_list_login_history accept? +

logi_list_login_history accepts 1 parameter: limit. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on logi_list_login_history? +

Register the 1pass MCP server in PolicyLayer and add a rule for logi_list_login_history: 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.

What risk level is logi_list_login_history? +

logi_list_login_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit logi_list_login_history? +

Yes. Add a rate_limit block to the logi_list_login_history 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.

How do I block logi_list_login_history completely? +

Set action: deny in the PolicyLayer policy for logi_list_login_history. 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.

What MCP server provides logi_list_login_history? +

logi_list_login_history 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.

KEEP EXPLORING

More on 1pass, and thousands of servers like it.

This server

All 15 1pass tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →