132 tools. 57 can modify or destroy data without limits.
15 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (fleet_delete_bootstrap_package, fleet_delete_host, fleet_delete_invite) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (fleet_add_app_store_app, fleet_add_labels_to_host, fleet_add_team_users) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (fleet_install_software, fleet_lock_device, fleet_lock_host) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Fleet. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @fleet-mcp fleet_delete_bootstrap_package:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
fleet_add_app_store_app:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
fleet_find_software_on_host:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Fleet server exposes 15 destructive tools including fleet_delete_bootstrap_package, fleet_delete_host, fleet_delete_invite. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Fleet server has 32 write tools including fleet_add_app_store_app, fleet_add_labels_to_host, fleet_add_team_users. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
132 tools across 4 categories: Destructive, Execute, Read, Write. 75 are read-only. 57 can modify, create, or delete data.
One line change. Instead of running the Fleet server directly, prefix it with Intercept: intercept -c io-github-simplyminimal-fleet-mcp.yaml -- npx -y @fleet-mcp. Download a pre-built policy from policylayer.com/policies/io-github-simplyminimal-fleet-mcp and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init