delete_senderid

Delete a registered sender phone number. SAFETY: requires confirmed=true. solactl is invoked with --yes to skip its own interactive prompt.

Server SOLAPI MCP Server solapi/solapi-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_senderid does on SOLAPI MCP Server

AI agents call delete_senderid to permanently remove resources in SOLAPI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_senderid needs a policy

This tool permanently removes a sender phone number registration, which cannot be undone. Although it includes a safety guard (requires confirmed=true), the core operation is destructive. The blast radius is high because deleting a sender ID could break active messaging workflows, prevent legitimate SMS/MMS campaigns, or impact business continuity.

From the tool's definition Tool name is 'delete_senderid' and description states 'Delete a registered sender phone number.' The verb 'delete' indicates irreversible removal of data.

Questions about delete_senderid

What does the delete_senderid tool do? +

Delete a registered sender phone number. SAFETY: requires confirmed=true. solactl is invoked with --yes to skip its own interactive prompt. It is categorised as a Destructive tool in the SOLAPI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_senderid? +

Register the SOLAPI MCP Server MCP server in PolicyLayer and add a rule for delete_senderid: 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 SOLAPI MCP Server. Nothing to install.

What risk level is delete_senderid? +

delete_senderid is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_senderid? +

Yes. Add a rate_limit block to the delete_senderid 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.

How do I block delete_senderid completely? +

Set action: deny in the PolicyLayer policy for delete_senderid. 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.

What MCP server provides delete_senderid? +

delete_senderid is provided by the SOLAPI MCP Server MCP server (solapi/solapi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.