update_senderid · SOLAPI MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_senderid does on SOLAPI MCP Server

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

WHY IT NEEDS A POLICY

Why update_senderid needs a policy

This tool changes the operational status of a sender phone number, which is a reversible configuration modification. It does not delete data (would be Destructive) nor move money (Financial). The confirmed=true requirement reduces risk but the tool still modifies messaging infrastructure state.

From the tool's definition update_senderid: 'Activate or deactivate a registered sender phone number' — modifies the state of a sender ID (a communication resource) reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_senderid Rate-limited

update_senderid 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_senderid": {
      "limits": [
        {
          "counter": "update_senderid_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SOLAPI MCP Server, so you can run agents against it safely.

FAQ

Questions about update_senderid

What does the update_senderid tool do? +

Activate or deactivate a registered sender phone number. SAFETY: requires confirmed=true. It is categorised as a Write tool in the SOLAPI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_senderid? +

Register the SOLAPI MCP Server MCP server in PolicyLayer and add a rule for update_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 update_senderid? +

update_senderid is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_senderid? +

Yes. Add a rate_limit block to the update_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 update_senderid completely? +

Set action: deny in the PolicyLayer policy for update_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 update_senderid? +

update_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.