find_cloud_diagrams
Use this when the user wants to find architecture diagrams or cloud infrastructure diagrams. Matches cloud resource IDs (cld_id or props.id) and returns diagram viewer URLs and image URLs. Creates a sheet filter and queues image rendering. Do NOT use this for cost analysis (use run_query) or inci...
This record as markdown: /tools/doit/find-cloud-diagrams.md
What find_cloud_diagrams does on Doit
AI agents call find_cloud_diagrams to retrieve information from Doit 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 |
|---|---|---|---|
resources | array | Yes | Cloud resource IDs matched against cld_id or props.id; these are not diagram component IDs. |
Parameters from the server's own tool schema.
Why find_cloud_diagrams is rated Low
Even though find_cloud_diagrams only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs find_cloud_diagrams safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_cloud_diagrams, this is the rule to start with:
find_cloud_diagrams 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 Doit, apply this rule, and every find_cloud_diagrams call is checked against it from then on.
Questions about find_cloud_diagrams
Use this when the user wants to find architecture diagrams or cloud infrastructure diagrams. Matches cloud resource IDs (cld_id or props.id) and returns diagram viewer URLs and image URLs. Creates a sheet filter and queues image rendering. Do NOT use this for cost analysis (use run_query) or incidents (use get_cloud_incidents). It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
find_cloud_diagrams accepts 1 parameter: resources. Required: resources. The full parameter table on this page comes from the server's own tool schema.
Register the Doit MCP server in PolicyLayer and add a rule for find_cloud_diagrams: 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 Doit. Nothing to install.
find_cloud_diagrams 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 find_cloud_diagrams 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 find_cloud_diagrams. 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.
find_cloud_diagrams is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Doit, and thousands of servers like it.
This server
Across the catalogue