logi_add_redirect_uri
Use when the user (RP owner) wants to register a new OAuth callback URL — for example after deploying to a new domain (easybracket.org), adding an iOS scheme, or staging environment. Idempotent: no-op if the URI is already registered. Server-side validators run (URI shape, sandbox host whitelist,...
This record as markdown: /tools/1pass-mcp/logi-add-redirect-uri.md
What logi_add_redirect_uri does on 1pass
AI agents use logi_add_redirect_uri 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 | |
uri | string | Yes |
Parameters from the server's own tool schema.
Why logi_add_redirect_uri is rated Medium
An AI agent can call logi_add_redirect_uri 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.
Risk signalsAccepts URL/endpoint input (uri)
Attacks that exploit this kind of access
The rule that runs logi_add_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_add_redirect_uri, this is the rule to start with:
logi_add_redirect_uri 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_add_redirect_uri call is checked against it from then on.
Questions about logi_add_redirect_uri
Use when the user (RP owner) wants to register a new OAuth callback URL — for example after deploying to a new domain (easybracket.org), adding an iOS scheme, or staging environment. Idempotent: no-op if the URI is already registered. Server-side validators run (URI shape, sandbox host whitelist, app_link host match) and the change is recorded in developer_audit_logs. Requires PAK scope apps:manage. Confirm with the user before calling — adding the wrong URI widens the attack surface for token interception. Pair with logi_show_app afterward to verify. 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_add_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_add_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_add_redirect_uri 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_add_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_add_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_add_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.
This server
Across the catalogue