dephq_project_validate
Validate the Dephq app source in a local directory without changing the remote app.
This record as markdown: /tools/dephq-mcp/dephq-project-validate.md
What dephq_project_validate does on Dephq
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_path | string | Yes |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs dephq_project_validate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dephq, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dephq_project_validate, this is the rule to start with:
dephq_project_validate 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 Dephq, apply this rule, and every dephq_project_validate call is checked against it from then on.
Questions about dephq_project_validate
Validate the Dephq app source in a local directory without changing the remote app. It is categorised as a Read tool in the Dephq MCP Server, which means it retrieves data without modifying state.
dephq_project_validate accepts 1 parameter: project_path. Required: project_path. The full parameter table on this page comes from the server's own tool schema.
Register the Dephq MCP server in PolicyLayer and add a rule for dephq_project_validate: 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 Dephq. Nothing to install.
dephq_project_validate 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 dephq_project_validate 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 dephq_project_validate. 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.
dephq_project_validate is provided by the Dephq MCP server (@dephq/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dephq, and thousands of servers like it.
This server
Across the catalogue