wait_for_otp

Block until an SMS OTP arrives for this session, then return the code. Polls the AgentSIM API for up to timeout_seconds. Returns the OTP code and the message it was extracted from. If the OTP does not arrive in time, raises a ToolError with advice on retrying. Always call release_number after you...

SERVERMcp SOURCEhttps://mcp.agentsim.dev/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/dev-agentsim-mcp/wait-for-otp.md

WHAT IT DOES

What wait_for_otp does on Mcp

AI agents call wait_for_otp to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`input`	object	Yes

Parameters from the server's own tool schema.

RISK

Why wait_for_otp is rated Low

The tool polls and retrieves an OTP code from an incoming SMS — it reads/fetches data without modifying or creating anything itself. However, the severity is medium because the OTP it returns could be used to authenticate into external accounts, meaning misuse could enable account takeovers even though the tool itself is purely read-oriented.

From the tool's definition Block until an SMS OTP arrives for this session, then return the code. Polls the AgentSIM API... Returns the OTP code and the message it was extracted from.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wait_for_otp safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wait_for_otp, this is the rule to start with:

wait_for_otp Allowed

wait_for_otp is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wait_for_otp": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every wait_for_otp call is checked against it from then on.

FAQ

Questions about wait_for_otp

What does the wait_for_otp tool do? +

What parameters does wait_for_otp accept? +

wait_for_otp accepts 1 parameter: input. Required: input. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on wait_for_otp? +

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

What risk level is wait_for_otp? +

wait_for_otp is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wait_for_otp? +

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

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

wait_for_otp is provided by the MCP server (https://mcp.agentsim.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 5 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →