Manage automation rules from remote agents

Remote agents can now manage Atoll automation rules with typed MCP tools in both the public plugin and full/private profiles. Atoll uses organization or project access for list and detail reads. Writes, tests, and run history require owner or admin access.

Keep new rules safe to review

Use atoll_create_automation_rule with an explicit project UUID or null for organization scope. A new rule always stays disabled. Update does not enable it; call the separate enable tool after a successful atoll_test_automation_rule dry run. The test preview does not execute actions.

Inspect bounded history

Use atoll_list_automation_runs to inspect up to 100 recent runs. The MCP response omits raw event payloads, action inputs, and free-form errors. The tools preserve Atoll authorization and conflict responses.

Use public integration tools safely

The public plugin can list redacted webhook metadata and delete a webhook. Webhook creation stays in the full/private profile because its response contains a one-time signing secret that ordinary tool output may retain. Public KPI HTTP sync tools create and validate drafts only; secret entry, network dry runs, publishing, and snapshot writes remain in Atoll.