get_cloud_diagram_resource_relationships
Use this when the user wants to understand how a specific resource in a cloud infrastructure diagram is connected to other resources — its upstream/downstream edges and optional group membership (only when kind is group_members or both). Returns the anchor resource plus up to 200 relations with t...
This record as markdown: /tools/doit/get-cloud-diagram-resource-relationships.md
What get_cloud_diagram_resource_relationships does on Doit
AI agents call get_cloud_diagram_resource_relationships 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 |
|---|---|---|---|
kind | string | — | Which relationship kinds to include. Possible values: edges, group_members, both (defaults to edges). |
depth | string | — | How far to traverse. Possible values: direct, transitive (defaults to direct). |
layerId | string | Yes | The diagram layer (statussheet) ID that contains the resource. |
direction | string | — | Relationship direction to traverse. Possible values: downstream, upstream, both (defaults to both). |
resourceId | string | Yes | The ID of the resource (node, element, or group) to map relationships for. |
Parameters from the server's own tool schema.
Why get_cloud_diagram_resource_relationships is rated Low
Even though get_cloud_diagram_resource_relationships 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_resource_relationships 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_resource_relationships, this is the rule to start with:
get_cloud_diagram_resource_relationships 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_resource_relationships call is checked against it from then on.
Questions about get_cloud_diagram_resource_relationships
Use this when the user wants to understand how a specific resource in a cloud infrastructure diagram is connected to other resources — its upstream/downstream edges and optional group membership (only when kind is group_members or both). Returns the anchor resource plus up to 200 relations with their type and hop distance; truncated is true when more than 200 relations exist. Requires the diagram layer ID and the resource ID. Do NOT use this for cost analysis (use get_cloud_diagram_cost_snapshot or run_query). It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
get_cloud_diagram_resource_relationships accepts 5 parameters: kind, depth, layerId, direction, resourceId. Required: layerId, resourceId. 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_resource_relationships: 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_resource_relationships 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_resource_relationships 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_resource_relationships. 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_resource_relationships 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