Use Automox with AI, safely
Sets up how an AI assistant works with your Automox console: confirms which account and organization it is reading, explains key-type 403 errors, and asks before any change.
Use it when
- You have just connected the Automox MCP server and want to know what it can do.
- A search returns a 403 and you need to know whether it is the key or your data.
- You are about to create, delete or apply something in Automox and want it confirmed first.
Tools it uses
advanced_device_searchcheck_group_exclusion_statuscheck_window_activeclone_policybatch_update_devicesdelete_action_sets_bulkapply_remediation_actionsapply_policy_changesdecide_patch_approvaldelete_devicedelete_policycreate_global_api_keycreate_user_api_keycreate_webhookcreate_data_extractcreate_saved_search
Check our Automox console for devices on the old policy, but only in the production organization.
I'm reading from the production organization, using the key it was connected with. The search returned 2 pages of results: 118 devices still on the legacy policy, and a sample of the first 10 is below. The advanced device search refused one filter with a 403, which usually means the key lacks access in this organization. Nothing has been changed. Do you want me to reassign these devices, and should I use an org-scoped key for the search?