# 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 have used the OTP.

Agent View of the PolicyLayer registry record for `wait_for_otp`. HTML page: https://policylayer.com/tools/dev-agentsim-mcp/wait-for-otp

## Facts

- Tool: `wait_for_otp`
- Server: Mcp (`https://mcp.agentsim.dev/mcp`) — https://policylayer.com/tools/dev-agentsim-mcp.md
- Homepage: https://github.com/agentsimdev/agentsim-mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `input` | object | yes |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "wait_for_otp",
    "arguments": {
      "input": {}
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

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

## Other tools on Mcp (4)

- `release_number` — Destructive — https://policylayer.com/tools/dev-agentsim-mcp/release-number.md
- `get_messages` — Read — https://policylayer.com/tools/dev-agentsim-mcp/get-messages.md
- `list_numbers` — Read — https://policylayer.com/tools/dev-agentsim-mcp/list-numbers.md
- `provision_number` — Write — https://policylayer.com/tools/dev-agentsim-mcp/provision-number.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-agentsim-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-agentsim-mcp