ENVIRONMENTS · DESKTOP AGENTS
An agent with your engineer’s
keys to production.
Coding agents run on developer machines with the developer’s full privileges — repos, credentials, cloud CLIs. TraceCtrl sees which agents and MCP servers are running, what they can reach, and stops the tool call that shouldn’t happen.
- Claude Code
- Cursor
- GitHub Copilot
- Codex
- Windsurf
- MCP servers
dev-machine-047 · senior engineer
2 agents · 5 MCP servers · 1 unapproved
The endpoint is the new agent perimeter.
.env in repo + agent reads project root + web tool
Credentials walk out in context
Cloud keys ingested into agent context are one poisoned instruction away from leaving the machine.
unapproved MCP server + broad tool grants + no allowlist
Supply chain, but for tools
A developer adds an MCP server from a gist; it now sits inside every session, shadowing legitimate tools.
agent = user identity + prod CLI access + yolo mode
Machine-speed actions, human blame
Every destructive action logs as the engineer. Without agent-level tracing you can't tell who — or what — did it.
HOW TRACECTRL COVERS DESKTOP AGENTS
Endpoint agent & MCP inventory
Which agents run on which machines, which MCP servers they load, what secrets sit in reach — with allowlist policy as posture.
AI-DR · PRIMARYIn-path tool-call enforcement
Guard sits between agent and tools: credential egress, unapproved MCP connections and destructive commands blocked before they execute.
AI-RED TEAMINGPoisoned-content drills
Seeds repos and docs with canary injections to prove which coding-agent setups actually leak — before a real gist does.