dephq_app_check
Run the platform runtime readiness checks for an owned app.
This record as markdown: /tools/dephq-mcp/dephq-app-check.md
What dephq_app_check does on Dephq
AI agents invoke dephq_app_check to trigger actions in Dephq. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes |
Parameters from the server's own tool schema.
Why dephq_app_check is rated High
The tool runs checks on a live app, which constitutes executing an operation against external infrastructure. While it appears to be read-only in intent (readiness checks), 'run' implies active execution of operations rather than passive data retrieval. Misuse risk is medium since it could trigger side effects on the platform or reveal sensitive configuration details.
From the tool's definition 'Run the platform runtime readiness checks' — actively executes checks against an app
Attacks that exploit this kind of access
The rule that runs dephq_app_check 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_app_check, this is the rule to start with:
dephq_app_check stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_app_check call is checked against it from then on.
Questions about dephq_app_check
Run the platform runtime readiness checks for an owned app. It is categorised as a Execute tool in the Dephq MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
dephq_app_check accepts 1 parameter: app_id. Required: app_id. 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_app_check: 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_app_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the dephq_app_check 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_app_check. 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_app_check 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