# dephq_apps_list

List apps owned by the authenticated Dephq creator.

Agent View of the PolicyLayer registry record for `dephq_apps_list`. HTML page: https://policylayer.com/tools/dephq-mcp/dephq-apps-list

## Facts

- Tool: `dephq_apps_list`
- Server: Dephq (`@dephq/mcp`) — https://policylayer.com/tools/dephq-mcp.md
- Install: `npx -y @dephq/mcp`
- Homepage: https://www.npmjs.com/package/@dephq/mcp
- 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": "dephq_apps_list",
    "arguments": {}
  }
}
```

## Why dephq_apps_list is rated Low

This tool retrieves and lists applications belonging to an authenticated user. It performs a read-only query with no side effects, no execution of code or commands, and no data modification. The severity is low because listing apps owned by an authenticated user represents minimal risk—the data returned is limited to resources the user already has access to.

From the tool's own definition: "Tool name 'dephq_apps_list' and description 'List apps owned by the authenticated Dephq creator' indicates a query/retrieval operation with no data modification."

## Use case

AI agents call dephq_apps_list to retrieve information from Dephq 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 Dephq:

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

## Other tools on Dephq (11)

- `dephq_app_unpublish` — Destructive — https://policylayer.com/tools/dephq-mcp/dephq-app-unpublish.md
- `dephq_app_check` — Execute — https://policylayer.com/tools/dephq-mcp/dephq-app-check.md
- `dephq_account` — Read — https://policylayer.com/tools/dephq-mcp/dephq-account.md
- `dephq_app_show` — Read — https://policylayer.com/tools/dephq-mcp/dephq-app-show.md
- `dephq_app_versions` — Read — https://policylayer.com/tools/dephq-mcp/dephq-app-versions.md
- `dephq_project_validate` — Read — https://policylayer.com/tools/dephq-mcp/dephq-project-validate.md
- `dephq_sync_status` — Read — https://policylayer.com/tools/dephq-mcp/dephq-sync-status.md
- `dephq_app_publish` — Write — https://policylayer.com/tools/dephq-mcp/dephq-app-publish.md
- `dephq_app_rollback` — Write — https://policylayer.com/tools/dephq-mcp/dephq-app-rollback.md
- `dephq_project_init` — Write — https://policylayer.com/tools/dephq-mcp/dephq-project-init.md
- `dephq_project_sync` — Write — https://policylayer.com/tools/dephq-mcp/dephq-project-sync.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=dephq-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dephq-mcp