dials_deleteNumber
Release an owned number at its carrier through DELETE (DELETE /v1/dials/numbers/{number_id}) [service status: unverified]
This record as markdown: /tools/lifesi-genesis-mcp/dials-deletenumber.md
What dials_deleteNumber does on Genesis
AI agents call dials_deleteNumber to permanently remove resources in Genesis, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | |
actorId | string | Yes | |
number_id | string | Yes | |
projectId | string | Yes | Selected Dials scope. |
platformId | string | — | Selected data platform. Omitted defaults to dials in the backend; selection does not grant organization authority. |
workspaceId | string | Yes | Selected Dials scope. |
environmentId | string | Yes | Selected Dials scope. |
organizationId | string | Yes | Must match the authenticated organization. |
Parameters from the server's own tool schema.
Why dials_deleteNumber is rated Critical
An AI agent that decides to call dials_deleteNumber doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Genesis is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs dials_deleteNumber safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dials_deleteNumber, this is the rule to start with:
dials_deleteNumber 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 Genesis, apply this rule, and every dials_deleteNumber call is checked against it from then on.
Questions about dials_deleteNumber
Release an owned number at its carrier through DELETE (DELETE /v1/dials/numbers/{number_id}) [service status: unverified]. It is categorised as a Destructive tool in the Genesis MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
dials_deleteNumber accepts 8 parameters: reason, actorId, number_id, projectId, platformId, workspaceId, environmentId, organizationId. Required: actorId, number_id, projectId, workspaceId, environmentId, organizationId. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for dials_deleteNumber: 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 Genesis. Nothing to install.
dials_deleteNumber 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 dials_deleteNumber 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 dials_deleteNumber. 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.
dials_deleteNumber is provided by the Genesis MCP server (@lifesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
Across the catalogue