wizard_update_onboarding_state

THE RISK

Medium Risk

Why wizard_update_onboarding_state needs a policy

This tool modifies onboarding state reversibly (Write category), not irreversibly. The blast radius is medium because incorrect onboarding state updates could disrupt contact center setup workflows and affect multiple users, but the change appears reversible.

From the tool's definition Tool name 'wizard_update_onboarding_state' indicates it updates/modifies state of an onboarding process. The 'update' verb and '_state' suffix suggest persistent modification of onboarding configuration or status within an Amazon Connect contact center system.

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

POLICY

How to control wizard_update_onboarding_state

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_update_onboarding_state:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wizard_update_onboarding_state": {
      "limits": [
        {
          "counter": "wizard_update_onboarding_state_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

wizard_update_onboarding_state stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Amazon Connect MCP Server tools

Execute wizard_execute_onboarding wizard_execute_onboarding Execute wizard_start_setup wizard_start_setup Write wizard_generate_faq_files wizard_generate_faq_files 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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about wizard_update_onboarding_state

What does the wizard_update_onboarding_state tool do? +

wizard_update_onboarding_state. It is categorised as a Write tool in the Amazon Connect MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wizard_update_onboarding_state? +

Register the Amazon Connect MCP Server MCP server in PolicyLayer and add a rule for wizard_update_onboarding_state: 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_update_onboarding_state? +

wizard_update_onboarding_state is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wizard_update_onboarding_state? +

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

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

wizard_update_onboarding_state 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 →