AI agents invoke wizard_start_setup to trigger actions in Amazon Connect MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Setup wizards in contact center systems typically execute infrastructure or configuration changes with external effects (e.g., creating routing rules, deploying workflows, configuring IVR systems). These actions trigger operations whose effects depend on execution context and parameters, fitting the Execute category.
From the tool's definition Tool name is 'wizard_start_setup' which suggests initiating a setup process. Given the context of Amazon Connect contact center infrastructure and sibling tools like 'wizard_execute_onboarding' and 'wizard_discover_website', this tool likely triggers…
Documented attack patterns abuse exactly the kind of access wizard_start_setup gives an agent:
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_start_setup:
{
"version": "1",
"default": "deny",
"tools": {
"wizard_start_setup": {
"limits": [
{
"counter": "wizard_start_setup_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} wizard_start_setup 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.
Free to start. No card required.
wizard_start_setup. 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.
Register the Amazon Connect MCP Server MCP server in PolicyLayer and add a rule for wizard_start_setup: 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.
wizard_start_setup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wizard_start_setup 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.
Set action: deny in the PolicyLayer policy for wizard_start_setup. 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.
wizard_start_setup 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.
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.
Free to start. No card required.
12 Amazon Connect MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.