get_topology
Retrieve infrastructure topology graphs showing resources and relationships across connectors to understand workload placement, ownership, and scope membership.
Instructions
Return the infrastructure topology graph (Resources and Edges) from every topology-capable connector. When to use: when an agent needs to reason about which workload runs on which host, who owns whom, or which scope (namespace/project/folder) a resource belongs to. Pair with get_blast_radius for shared-host RCA. Behavior: read-only, no side effects. Returns { sources, resources, edges, total, truncated }. Filters compose: source to one connector, kind to one resource type (e.g. 'pod', 'node', 'deployment'), scope to members of a namespace/folder/project. Output is capped by limit (default 500, max 5000) and edges referencing dropped resources are removed. Related: get_blast_radius to evaluate the impact of a host failure; list_sources to discover topology-capable connectors.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| source | No | Optional. Restrict the graph to one topology connector by source name (see `list_sources`). Default: merge across all connectors. | |
| kind | No | Optional. Restrict to resources of one kind. Common values for Kubernetes: 'pod', 'node', 'deployment', 'replicaset', 'namespace'. Other connectors may emit different kinds (e.g. 'vm', 'hypervisor', 'volume'). Default: all kinds. | |
| scope | No | Optional. Restrict to resources contained in a scope (anything pointed to by `IN_NAMESPACE` edges). Pass the scope's resource id (e.g. 'k8s:namespace:default') or its name (e.g. 'default'). Default: no scope filter. | |
| limit | No | Optional. Maximum resources to return; edges are trimmed to the kept set. Default 500, max 5000. |