list_env
List a DenkOps project's environment variable KEYS (values are write-only and never shown). Includes whether changes are pending a redeploy.
This record as markdown: /tools/denkopsai-mcp/list-env.md
What list_env does on Denkopsai
AI agents call list_env to retrieve information from Denkopsai 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_id | string | Yes |
Parameters from the server's own tool schema.
Why list_env is rated Low
This tool performs a query/list operation to retrieve environment variable metadata (keys and deployment status) from a DenkOps project. It has no capability to modify, delete, or execute operations — it simply returns information. The write-only nature of values means the tool cannot expose sensitive data, further reducing risk. This is a classic Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description explicitly states 'List a DenkOps project's environment variable KEYS' — the action is to retrieve/list data.
Attacks that exploit this kind of access
The rule that runs list_env safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_env, this is the rule to start with:
list_env 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 Denkopsai, apply this rule, and every list_env call is checked against it from then on.
Questions about list_env
List a DenkOps project's environment variable KEYS (values are write-only and never shown). Includes whether changes are pending a redeploy. It is categorised as a Read tool in the Denkopsai MCP Server, which means it retrieves data without modifying state.
list_env accepts 1 parameter: project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai MCP server in PolicyLayer and add a rule for list_env: 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 Denkopsai. Nothing to install.
list_env 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 list_env 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 list_env. 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.
list_env is provided by the Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denkopsai, and thousands of servers like it.
This server
Across the catalogue