logi_delete_login_log
Use when the user wants to remove a specific login record from view (e.g. 'delete that suspicious entry'). Soft-delete only — recoverable for 90 days. Requires the row id from logi_list_login_history. Do NOT use this to revoke a session or block future logins; that's a different scope.
This record as markdown: /tools/1pass-mcp/logi-delete-login-log.md
What logi_delete_login_log does on 1pass
AI agents call logi_delete_login_log to permanently remove resources in 1pass, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes |
Parameters from the server's own tool schema.
Why logi_delete_login_log is rated Critical
An AI agent that decides to call logi_delete_login_log doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from 1pass is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs logi_delete_login_log 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_delete_login_log, this is the rule to start with:
logi_delete_login_log is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 1pass, apply this rule, and every logi_delete_login_log call is checked against it from then on.
Questions about logi_delete_login_log
Use when the user wants to remove a specific login record from view (e.g. 'delete that suspicious entry'). Soft-delete only — recoverable for 90 days. Requires the row id from logi_list_login_history. Do NOT use this to revoke a session or block future logins; that's a different scope. It is categorised as a Destructive tool in the 1pass MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
logi_delete_login_log accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the 1pass MCP server in PolicyLayer and add a rule for logi_delete_login_log: 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_delete_login_log is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the logi_delete_login_log 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_delete_login_log. 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_delete_login_log 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.
Across the catalogue