# provision_number

Lease a temporary programmable phone number for receiving SMS OTP codes. Returns the phone number (e164 format) and a session_id needed for all subsequent calls. The number is reserved for your session for ttl_seconds. Next step: use the returned number on your target service to trigger an SMS, then call wait_for_otp with the returned session_id.

Agent View of the PolicyLayer registry record for `provision_number`. HTML page: https://policylayer.com/tools/dev-agentsim-mcp/provision-number

## Facts

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

## 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": "provision_number",
    "arguments": {
      "input": {}
    }
  }
}
```

## Why provision_number is rated Medium

This tool provisions (creates/reserves) a temporary phone number resource tied to a session. It is a Write operation because it allocates a new resource reversibly — the number can be released (sibling tool 'release_number' exists).

From the tool's own definition: "'Lease a temporary programmable phone number' and 'The number is reserved for your session for ttl_seconds' — creates/reserves a resource with a defined lifetime"

Risk signals: Accepts URL/endpoint input (input.webhook_url)

## Use case

AI agents use provision_number to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "provision_number": {
      "limits": [
        {
          "counter": "provision_number_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## 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
- `wait_for_otp` — Read — https://policylayer.com/tools/dev-agentsim-mcp/wait-for-otp.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