Tool footprint
Tool footprint
Section titled “Tool footprint”Tool footprint is the per-session inventory of every tool and MCP call the agent made.
"Called gmail.send 3×, slack.post 1×, github.search 12×, internal-mcp/jira/create 1×." Plus what arguments, plus who/what was on the receiving end.
Footprint is derived, not stored separately — it's a query over the audit trail's tool-call events.
At a glance
Section titled “At a glance”| Derived from | Audit trail events tagged tool.call and mcp.call |
| Scoped to | one Session (typical) or aggregated across sessions |
| Grouped by | tool id → target (recipient, repo, channel, …) |
| Surfaces | Sessions UI per-session detail · per-agent rollup · compliance reports |
| Status | next |
What it shows
Section titled “What it shows”For a single session:
| Tool | Calls | Targets | Notable |
|---|---|---|---|
gmail.send | 3 | 2 unique recipients | 1 outside org domain — flagged |
github.search | 12 | 4 repos | all in catalog |
internal-mcp/jira/create | 1 | project KEY-123 | ticket created |
slack.post | 1 | #support-bots | within allowed channel list |
Per-agent and per-project rollups answer: "which tools does this agent reach for? where does it write data? what's the blast radius if it goes wrong?"
Why this is its own concept
Section titled “Why this is its own concept”Footprint is the outbound view of a session: every external action the agent took. It complements:
- Pipeline findings — what the pipeline caught
- Metering — what it cost
- Footprint — what the agent did
Three projections of the same session data, each tuned for a different operator question.
Footprint is also the input to:
- Catalog completeness. Calls to uncatalogued tools land in Tool discovery for review.
- Anomaly detection. Footprint baselines drive drift detection — "this agent has never written to this repo before."
- Compliance evidence. "All external email recipients in Q2" — a footprint query.
Surfaces
Section titled “Surfaces”| Persona | Surface | What they see |
|---|---|---|
| Operator | Sessions detail page → Footprint tab | Per-session inventory, drill into each call |
| Operator | Agent dashboard → Tools rollup | Most-called tools, anomalous targets |
| Auditor | Compliance report | Footprint filtered by tool category (e.g., outbound communication) |
| Catalog reviewer | Tool discovery queue | Footprint calls to uncatalogued tools |
Related concepts
Section titled “Related concepts”- derived from ← Audit trail
- scoped to ← Session
- groups by → Tool catalog entries
- feeds → Tool discovery, drift baselines
- adjacent to ↔ Pipeline findings, Metering