get_statussheet_components
Cloud Diagrams visualize your cloud infrastructure and resource relationships. Returns the specified components of a diagram layer. Provide at least one component type with one or more IDs in the request body (for example, node or element).
This record as markdown: /tools/doit/get-statussheet-components.md
What get_statussheet_components does on Doit
AI agents call get_statussheet_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 |
|---|---|---|---|
p | string | — | |
id | string | Yes | |
link | array | — | Link IDs to fetch. |
node | array | — | Node IDs to fetch. |
note | array | — | Note IDs to fetch. |
group | array | — | Group IDs to fetch. |
element | array | — | Element IDs to fetch. |
combiner | array | — | Combiner IDs to fetch. |
attachment | array | — | Attachment IDs to fetch. |
customerContext | string | — | Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users. |
Parameters from the server's own tool schema.
Why get_statussheet_components is rated Low
Even though get_statussheet_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.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs get_statussheet_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_statussheet_components, this is the rule to start with:
get_statussheet_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_statussheet_components call is checked against it from then on.
Questions about get_statussheet_components
Cloud Diagrams visualize your cloud infrastructure and resource relationships. Returns the specified components of a diagram layer. Provide at least one component type with one or more IDs in the request body (for example, node or element). It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.
get_statussheet_components accepts 10 parameters: p, id, link, node, note, group, element, combiner, attachment, customerContext. Required: id. 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_statussheet_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_statussheet_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_statussheet_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_statussheet_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_statussheet_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