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, t...
This record as markdown: /tools/dev-agentsim-mcp/provision-number.md
What provision_number does on Mcp
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
input | object | Yes |
Parameters from the server's own tool schema.
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 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 signalsAccepts URL/endpoint input (input.webhook_url)
Attacks that exploit this kind of access
The rule that runs provision_number 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 provision_number, this is the rule to start with:
provision_number 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every provision_number call is checked against it from then on.
Questions about 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. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
provision_number accepts 1 parameter: input. Required: input. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for provision_number: 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.
provision_number is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the provision_number 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.
Set action: deny in the PolicyLayer policy for provision_number. 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.
provision_number 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.
More on , and thousands of servers like it.
This server
Across the catalogue