wait_for_user

wait_for_user

Server Voice voice-mcp-server
Category Execute
Risk class High
Parameters 00 required

What wait_for_user does on Voice

AI agents invoke wait_for_user to trigger actions in Voice. 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.

Why wait_for_user needs a policy

wait_for_user triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Questions about wait_for_user

What does the wait_for_user tool do? +

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

How do I enforce a policy on wait_for_user? +

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

What risk level is wait_for_user? +

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

Can I rate-limit wait_for_user? +

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

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

wait_for_user is provided by the Voice MCP server (voice-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.