list_domains
List a DenkOps project's custom domains and whether each is verified.
This record as markdown: /tools/denkopsai-mcp/list-domains.md
What list_domains does on Denkopsai
AI agents call list_domains 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_domains is rated Low
This tool only queries and returns information about existing domains associated with a project. It performs no mutations, deletions, or external operations. The blast radius of misuse is minimal—an agent could only view domain configuration data, which is low-sensitivity metadata. No side effects or irreversible actions are possible.
From the tool's definition Tool name 'list_domains' and description 'List a DenkOps project's custom domains and whether each is verified' indicate a read-only operation that retrieves domain information without modifying or deleting data.
Attacks that exploit this kind of access
The rule that runs list_domains 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_domains, this is the rule to start with:
list_domains 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_domains call is checked against it from then on.
Questions about list_domains
List a DenkOps project's custom domains and whether each is verified. It is categorised as a Read tool in the Denkopsai MCP Server, which means it retrieves data without modifying state.
list_domains 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_domains: 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_domains 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_domains 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_domains. 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_domains 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