get_cloud_diagram_components
Use this when the user wants to discover all cloud infrastructure diagrams and their layers (statussheets), or to look up layer IDs needed for other diagram endpoints. With no filters, returns accessible application and infrastructure diagrams with layer metadata and no component data. Returns ma...
This record as markdown: /tools/doit/get-cloud-diagram-components.md
What get_cloud_diagram_components does on Doit
AI agents call get_cloud_diagram_components 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 |
|---|---|---|---|
layer_ids | array | — | Select these layer (statussheet) IDs and their owning diagrams. Component data is loaded only for selected layers, or resolved diagram layers when include_compo |
scheme_ids | array | — | Select these diagram IDs. When combined with layer_ids, also returns the diagrams owning those layers. |
skip_empty | boolean | — | Omit empty layers from each diagram's layer metadata; diagrams remain in the result. Defaults to false. |
include_components | boolean | — | Load component maps for up to five selected layers, or resolved diagram layers when layer_ids is omitted. Larger selections return an error; discover layer IDs |
Parameters from the server's own tool schema.
Why get_cloud_diagram_components is rated Low
Even though get_cloud_diagram_components 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 get_cloud_diagram_components 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 get_cloud_diagram_components, this is the rule to start with:
get_cloud_diagram_components 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 get_cloud_diagram_components call is checked against it from then on.
Questions about get_cloud_diagram_components
Use this when the user wants to discover all cloud infrastructure diagrams and their layers (statussheets), or to look up layer IDs needed for other diagram endpoints. With no filters, returns accessible application and infrastructure diagrams with layer metadata and no component data. Returns maps keyed by diagram and layer IDs. Selectors must belong to diagrams accessible to the authenticated customer and user. scheme_ids and the diagrams owning layer_ids are combined, not intersected. The layer IDs required by other diagram tools come from this tool. Optionally filter by diagram IDs (scheme_ids) or layer IDs (layer_ids), and set include_components=true to load projected component maps for up to five requested or resolved layers. Larger selections return an error before loading components; discover metadata first, then request batches of at most five layer_ids. Do NOT use this for cost analysis (use run_query) or diagram search (use search_cloud_diagrams). It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
get_cloud_diagram_components accepts 4 parameters: layer_ids, scheme_ids, skip_empty, include_components. 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 get_cloud_diagram_components: 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.
get_cloud_diagram_components 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 get_cloud_diagram_components 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 get_cloud_diagram_components. 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.
get_cloud_diagram_components 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