# dephq_project_validate

Validate the Dephq app source in a local directory without changing the remote app.

Agent View of the PolicyLayer registry record for `dephq_project_validate`. HTML page: https://policylayer.com/tools/dephq-mcp/dephq-project-validate

## Facts

- Tool: `dephq_project_validate`
- 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: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `project_path` | string | yes |  |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "dephq_project_validate",
    "arguments": {
      "project_path": "<project_path>"
    }
  }
}
```

## Why dephq_project_validate is rated Low

This tool performs a read-only validation check on local app source code. It retrieves or analyzes data (the local directory contents and their validity) with no side effects—it neither modifies, deletes, executes external operations, nor affects the remote application. This is a classic Read category action.

From the tool's own definition: "Tool description states 'Validate the Dephq app source in a local directory without changing the remote app.' The key phrase 'without changing the remote app' explicitly indicates no modifications occur. Validation is an inspection/verification operation."

## Use case

AI agents call dephq_project_validate 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_project_validate": {}
  }
}
```

## 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_apps_list` — Read — https://policylayer.com/tools/dephq-mcp/dephq-apps-list.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