logi_restore_login_log
Use when the user wants to undo a deletion ('restore that log', 'I deleted the wrong one'). Takes an id from logi_list_trashed_logs. Idempotent — restoring an already-restored row is a no-op.
This record as markdown: /tools/1pass-mcp/logi-restore-login-log.md
What logi_restore_login_log does on 1pass
AI agents use logi_restore_login_log to create or update resources in 1pass, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 1pass environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes |
Parameters from the server's own tool schema.
Why logi_restore_login_log is rated Medium
An AI agent can call logi_restore_login_log faster than any human can review: one bad instruction and it creates or modifies resources in 1pass by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs logi_restore_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_restore_login_log, this is the rule to start with:
logi_restore_login_log stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_restore_login_log call is checked against it from then on.
Questions about logi_restore_login_log
Use when the user wants to undo a deletion ('restore that log', 'I deleted the wrong one'). Takes an id from logi_list_trashed_logs. Idempotent — restoring an already-restored row is a no-op. It is categorised as a Write tool in the 1pass MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
logi_restore_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_restore_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_restore_login_log is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the logi_restore_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_restore_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_restore_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.
This server
Across the catalogue