wizard_execute_onboarding

THE RISK

High Risk

Why wizard_execute_onboarding needs a policy

Despite the empty description, the tool name 'execute' paired with 'onboarding' in an Amazon Connect context indicates this tool triggers external operations or state changes in a contact center system. Onboarding workflows typically involve provisioning, configuration, and initialization of services—actions whose effects depend on provided arguments and cannot be safely reversed without manual intervention.

From the tool's definition Tool name 'wizard_execute_onboarding' contains 'execute' and 'onboarding'; part of Amazon Connect MCP server that 'enables AI assistants to interact with Amazon Connect contact centers.' The 'execute' verb combined with onboarding context suggests triggering…

Documented attack patterns abuse exactly the kind of access wizard_execute_onboarding gives an agent:

POLICY

How to control wizard_execute_onboarding

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Connect MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wizard_execute_onboarding:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wizard_execute_onboarding": {
      "limits": [
        {
          "counter": "wizard_execute_onboarding_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

wizard_execute_onboarding stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Amazon Connect MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Amazon Connect MCP Server tools

Execute wizard_start_setup wizard_start_setup Write wizard_generate_faq_files wizard_generate_faq_files Write wizard_update_onboarding_state wizard_update_onboarding_state Read layout_visualizer layout_visualizer Other template_customize template_customize Read template_get template_get Read template_get_case_workflow template_get_case_workflow Read template_get_routing_workflow template_get_routing_workflow

All 12 Amazon Connect MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Amazon Connect MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about wizard_execute_onboarding

What does the wizard_execute_onboarding tool do? +

wizard_execute_onboarding. It is categorised as a Execute tool in the Amazon Connect MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wizard_execute_onboarding? +

Register the Amazon Connect MCP Server MCP server in PolicyLayer and add a rule for wizard_execute_onboarding: 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 Amazon Connect MCP Server. Nothing to install.

What risk level is wizard_execute_onboarding? +

wizard_execute_onboarding is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wizard_execute_onboarding? +

Yes. Add a rate_limit block to the wizard_execute_onboarding 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 wizard_execute_onboarding completely? +

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

wizard_execute_onboarding is provided by the Amazon Connect MCP Server MCP server (mundurragacl/amazon-connect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Connect MCP Server tool call.

Start from Amazon Connect MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →