logi_get_doc
Use when the user asks about a specific logi/1pass topic (OAuth scopes, PKCE, redirect URI rules, CLI commands, security model, panopticon, agent approval, etc.) and you need the canonical doc text. Read-only, no auth required (fetches public docs.1pass.dev/llms/{path}). Path must be like 'oauth/...
This record as markdown: /tools/1pass-mcp/logi-get-doc.md
What logi_get_doc does on 1pass
AI agents call logi_get_doc 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 |
|---|---|---|---|
path | string | Yes |
Parameters from the server's own tool schema.
Why logi_get_doc is rated Low
Even though logi_get_doc 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.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs logi_get_doc 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_get_doc, this is the rule to start with:
logi_get_doc is read-only, so it stays allowed. 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_get_doc call is checked against it from then on.
Questions about logi_get_doc
Use when the user asks about a specific logi/1pass topic (OAuth scopes, PKCE, redirect URI rules, CLI commands, security model, panopticon, agent approval, etc.) and you need the canonical doc text. Read-only, no auth required (fetches public docs.1pass.dev/llms/{path}). Path must be like 'oauth/scopes.md', 'guide/security.md', 'cli/overview.md'. Allowed prefixes: guide/, oauth/, integrations/, tracks/, cli/, reference/, security/, operations/, panopticon/, agent-approval/, compare/. Discover available paths via logi_list_docs first. It is categorised as a Read tool in the 1pass MCP Server, which means it retrieves data without modifying state.
logi_get_doc accepts 1 parameter: path. Required: path. 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_get_doc: 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_get_doc is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the logi_get_doc 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_get_doc. 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_get_doc 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