This record as markdown: /tools/dev-agentsim-mcp/release-number.md
What release_number does on Mcp
AI agents call release_number to permanently remove resources in Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
input | object | Yes |
Parameters from the server's own tool schema.
Why release_number is rated Critical
Releasing a provisioned number is an irreversible action: once returned to the pool, the number is no longer associated with the agent's session and cannot be reclaimed. Any pending messages or OTP codes tied to that number would be lost. This constitutes an irreversible destruction of an allocated resource, placing it firmly in the Destructive category.
From the tool's definition Release a provisioned number back to the pool — this permanently deallocates the provisioned mobile number, making it unavailable for further use in the current session and potentially losing any associated messages or OTP state.
Attacks that exploit this kind of access
The rule that runs release_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 release_number, this is the rule to start with:
release_number is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every release_number call is checked against it from then on.
Questions about release_number
Release a provisioned number back to the pool. Always call this when you are done with the session — even on error — to avoid consuming pool capacity unnecessarily. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
release_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 release_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.
release_number is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the release_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 release_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.
release_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