# logi_list_apps

Use when the user (as a developer) asks 'what OAuth apps do I own?', 'list my RPs', or needs the app id before adding/removing a redirect_uri. Read-only. Returns id, name, client_id, status, and current redirect_uris for every app the PAK owner can manage. Requires PAK scope apps:read or apps:manage. Do NOT use to list end-user authorized apps — that's logi_list_connected_apps.

Agent View of the PolicyLayer registry record for `logi_list_apps`. HTML page: https://policylayer.com/tools/1pass-mcp/logi-list-apps

## Facts

- Tool: `logi_list_apps`
- Server: 1pass (`@1pass/mcp`) — https://policylayer.com/tools/1pass-mcp.md
- Install: `npx -y @1pass/mcp`
- Homepage: https://github.com/dcode-co/logi-plugins
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "logi_list_apps",
    "arguments": {}
  }
}
```

## Why logi_list_apps is rated Low

Even though logi_list_apps 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 signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call logi_list_apps 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 1pass:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "logi_list_apps": {}
  }
}
```

## Other tools on 1pass (14)

- `logi_delete_login_log` — Destructive — https://policylayer.com/tools/1pass-mcp/logi-delete-login-log.md
- `logi_delete_passkey` — Destructive — https://policylayer.com/tools/1pass-mcp/logi-delete-passkey.md
- `logi_remove_redirect_uri` — Destructive — https://policylayer.com/tools/1pass-mcp/logi-remove-redirect-uri.md
- `logi_fetch_quickstart` — Read — https://policylayer.com/tools/1pass-mcp/logi-fetch-quickstart.md
- `logi_get_doc` — Read — https://policylayer.com/tools/1pass-mcp/logi-get-doc.md
- `logi_list_connected_apps` — Read — https://policylayer.com/tools/1pass-mcp/logi-list-connected-apps.md
- `logi_list_docs` — Read — https://policylayer.com/tools/1pass-mcp/logi-list-docs.md
- `logi_list_login_history` — Read — https://policylayer.com/tools/1pass-mcp/logi-list-login-history.md
- `logi_list_passkeys` — Read — https://policylayer.com/tools/1pass-mcp/logi-list-passkeys.md
- `logi_list_trashed_logs` — Read — https://policylayer.com/tools/1pass-mcp/logi-list-trashed-logs.md
- `logi_show_app` — Read — https://policylayer.com/tools/1pass-mcp/logi-show-app.md
- `logi_whoami` — Read — https://policylayer.com/tools/1pass-mcp/logi-whoami.md
- `logi_add_redirect_uri` — Write — https://policylayer.com/tools/1pass-mcp/logi-add-redirect-uri.md
- `logi_restore_login_log` — Write — https://policylayer.com/tools/1pass-mcp/logi-restore-login-log.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=1pass-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/1pass-mcp