Critical Risk →

fleet_delete_setup_assistant

Delete the MDM Apple Setup Assistant config

Risk signalsRemoves device onboarding configuration

Part of the Fleet server.

fleet_delete_setup_assistant can permanently delete data in Fleet, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE FLEET →

Free to start. No card required.

AI agents may call fleet_delete_setup_assistant to permanently remove or destroy resources in Fleet. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call fleet_delete_setup_assistant in a loop, permanently destroying resources in Fleet. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "fleet_delete_setup_assistant"
  ]
}

See the full Fleet policy for all 132 tools.

Get this rule live on your own Fleet server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FLEET →

View all 132 tools →

These attack patterns abuse exactly the kind of access fleet_delete_setup_assistant gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so fleet_delete_setup_assistant only ever does what you allow.

SECURE FLEET →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the fleet_delete_setup_assistant tool do? +

Delete the MDM Apple Setup Assistant config. It is categorised as a Destructive tool in the Fleet MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on fleet_delete_setup_assistant? +

Register the Fleet MCP server in PolicyLayer and add a rule for fleet_delete_setup_assistant: 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.

What risk level is fleet_delete_setup_assistant? +

fleet_delete_setup_assistant is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit fleet_delete_setup_assistant? +

Yes. Add a rate_limit block to the fleet_delete_setup_assistant 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.

How do I block fleet_delete_setup_assistant completely? +

Set action: deny in the PolicyLayer policy for fleet_delete_setup_assistant. 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.

What MCP server provides fleet_delete_setup_assistant? +

fleet_delete_setup_assistant is provided by the Fleet MCP server (fleet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fleet tool call.

Deterministic rules across all 132 Fleet tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.