list_cloud_diagram_node_activities
Use this when the user wants the change history of a single component node in a cloud diagram layer. Returns individual activity records (NODE_CREATE/NODE_UPDATE/NODE_DELETE) for the given node (ss_id + nodeId), ordered by timestamp descending, each including user as the ID of the user who made t...
This record as markdown: /tools/doit/list-cloud-diagram-node-activities.md
What list_cloud_diagram_node_activities does on Doit
AI agents call list_cloud_diagram_node_activities 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 |
|---|---|---|---|
limit | integer | — | Maximum number of records to return (default 50). |
ss_id | string | Yes | Layer ID the node belongs to. |
nodeId | string | Yes | Node component ID. |
offset | integer | — | Number of records to skip (default 0). |
Parameters from the server's own tool schema.
Why list_cloud_diagram_node_activities is rated Low
Even though list_cloud_diagram_node_activities 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 list_cloud_diagram_node_activities 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 list_cloud_diagram_node_activities, this is the rule to start with:
list_cloud_diagram_node_activities 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 list_cloud_diagram_node_activities call is checked against it from then on.
Questions about list_cloud_diagram_node_activities
Use this when the user wants the change history of a single component node in a cloud diagram layer. Returns individual activity records (NODE_CREATE/NODE_UPDATE/NODE_DELETE) for the given node (ss_id + nodeId), ordered by timestamp descending, each including user as the ID of the user who made the change. Page with offset/limit. 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.
list_cloud_diagram_node_activities accepts 4 parameters: limit, ss_id, nodeId, offset. Required: ss_id, nodeId. 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 list_cloud_diagram_node_activities: 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.
list_cloud_diagram_node_activities 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_cloud_diagram_node_activities 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_cloud_diagram_node_activities. 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_cloud_diagram_node_activities 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