This record as markdown: /tools/dephq-mcp/dephq-app-versions.md
What dephq_app_versions does on Dephq
AI agents call dephq_app_versions 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 |
|---|---|---|---|
app_id | string | Yes |
Parameters from the server's own tool schema.
Why dephq_app_versions is rated Low
This tool retrieves and displays historical version information about a Dephq app. It performs a query operation that reads data without side effects, reversible changes, or irreversible deletion. The severity is low because version history is typically non-sensitive metadata, and misuse would only expose information rather than cause damage or data loss.
From the tool's definition Tool name contains 'list' and description states 'List version history' — a retrieval operation with no modification or execution.
Attacks that exploit this kind of access
The rule that runs dephq_app_versions 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_versions, this is the rule to start with:
dephq_app_versions 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_app_versions call is checked against it from then on.
Questions about dephq_app_versions
List version history for an owned Dephq app. It is categorised as a Read tool in the Dephq MCP Server, which means it retrieves data without modifying state.
dephq_app_versions 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_versions: 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_versions 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_app_versions 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_versions. 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_versions 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