logi_remove_redirect_uri
Use when the user (RP owner) wants to deregister an old/unused OAuth callback URL — for example a historical onrender.com host that's been migrated to a custom domain. Refuses to remove the last remaining URI (would disable OAuth entirely). Server-side validators + audit log apply. Requires PAK s...
This record as markdown: /tools/1pass-mcp/logi-remove-redirect-uri.md
What logi_remove_redirect_uri does on 1pass
AI agents call logi_remove_redirect_uri 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 | |
uri | string | Yes |
Parameters from the server's own tool schema.
Why logi_remove_redirect_uri is rated Critical
An AI agent that decides to call logi_remove_redirect_uri 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.
Risk signalsAccepts URL/endpoint input (uri)
Attacks that exploit this kind of access
The rule that runs logi_remove_redirect_uri 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_remove_redirect_uri, this is the rule to start with:
logi_remove_redirect_uri 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_remove_redirect_uri call is checked against it from then on.
Questions about logi_remove_redirect_uri
Use when the user (RP owner) wants to deregister an old/unused OAuth callback URL — for example a historical onrender.com host that's been migrated to a custom domain. Refuses to remove the last remaining URI (would disable OAuth entirely). Server-side validators + audit log apply. Requires PAK scope apps:manage. Confirm with the user before calling. 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_remove_redirect_uri accepts 2 parameters: id, uri. Required: id, uri. 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_remove_redirect_uri: 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_remove_redirect_uri 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_remove_redirect_uri 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_remove_redirect_uri. 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_remove_redirect_uri 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