Snapshot the current outbound TCP flows for an app and report which destinations are NOT in the configured allowlist. Use to seed allowlists or audit unexpected egress. v1 is observe-only — it never blocks traffic.
AI agents call fleet_egress_snapshot to retrieve information from Fleet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries network flow data without side effects. It performs read-only observation of egress traffic to produce a report for auditing purposes. The explicit statement that it is 'observe-only' and 'never blocks traffic' confirms it has no destructive, write, or execution capabilities.
From the tool's definition Tool description states it 'snapshot[s] the current outbound TCP flows' and 'report[s]' results. Explicitly marked 'observe-only — it never blocks traffic.' No modification, deletion, or execution of external operations beyond passive observation.
Documented attack patterns abuse exactly the kind of access fleet_egress_snapshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fleet, and nothing reaches the server without passing your rules. This is the rule we recommend for fleet_egress_snapshot:
{
"version": "1",
"default": "deny",
"tools": {
"fleet_egress_snapshot": {}
}
}fleet_egress_snapshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Snapshot the current outbound TCP flows for an app and report which destinations are NOT in the configured allowlist. Use to seed allowlists or audit unexpected egress. v1 is observe-only — it never blocks traffic. It is categorised as a Read tool in the Fleet MCP Server, which means it retrieves data without modifying state.
Register the Fleet MCP server in PolicyLayer and add a rule for fleet_egress_snapshot: 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 Fleet. Nothing to install.
fleet_egress_snapshot 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 fleet_egress_snapshot 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 fleet_egress_snapshot. 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.
fleet_egress_snapshot is provided by the Fleet MCP server (wrxck/fleet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fleet, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
39 Fleet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.