Critical Risk →

modify_subscriber_status

Use this to change the OCS lifecycle status of a subscriber. Common transitions: ACTIVE → SUSPENDED (pause without losing packages), SUSPENDED → ACTIVE (reactivate), ACTIVE/SUSPENDED → TERMINATED (irreversible). WARNING: TERMINATED status is permanent — the subscriber record cannot be reactivated...

Part of the Carrier MCP: Give Your AI Agent Global Connectivity server.

modify_subscriber_status can permanently delete data in Carrier MCP: Give Your AI Agent Global Connectivity, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CARRIER MCP: GIVE YOUR AI AGENT GLOBAL CONNECTIVITY →

Free to start. No card required.

AI agents may call modify_subscriber_status to permanently remove or destroy resources in Carrier MCP: Give Your AI Agent Global Connectivity. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call modify_subscriber_status in a loop, permanently destroying resources in Carrier MCP: Give Your AI Agent Global Connectivity. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "modify_subscriber_status"
  ]
}

See the full Carrier MCP: Give Your AI Agent Global Connectivity policy for all 65 tools.

Get this rule live on your own Carrier MCP: Give Your AI Agent Global Connectivity server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CARRIER MCP: GIVE YOUR AI AGENT GLOBAL CONNECTIVITY →

View all 65 tools →

These attack patterns abuse exactly the kind of access modify_subscriber_status gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so modify_subscriber_status only ever does what you allow.

SECURE CARRIER MCP: GIVE YOUR AI AGENT GLOBAL CONNECTIVITY →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the modify_subscriber_status tool do? +

Use this to change the OCS lifecycle status of a subscriber. Common transitions: ACTIVE → SUSPENDED (pause without losing packages), SUSPENDED → ACTIVE (reactivate), ACTIVE/SUSPENDED → TERMINATED (irreversible). WARNING: TERMINATED status is permanent — the subscriber record cannot be reactivated. Params: iccid (subscriber identifier), status (new status string, e.g. 'ACTIVE', 'SUSPENDED', 'TERMINATED'). Returns: updated subscriber record with the new status. Do NOT use this to disable the SIM card at the network level — use change_sim_status for that. Always call get_subscriber first to confirm current status before modifying.. It is categorised as a Destructive tool in the Carrier MCP: Give Your AI Agent Global Connectivity 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 modify_subscriber_status? +

Register the Carrier MCP: Give Your AI Agent Global Connectivity MCP server in PolicyLayer and add a rule for modify_subscriber_status: 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 Carrier MCP: Give Your AI Agent Global Connectivity. Nothing to install.

What risk level is modify_subscriber_status? +

modify_subscriber_status 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 modify_subscriber_status? +

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

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

modify_subscriber_status is provided by the Carrier MCP: Give Your AI Agent Global Connectivity MCP server (carrier/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Carrier MCP: Give Your AI Agent Global Connectivity tool call.

Deterministic rules across all 65 Carrier MCP: Give Your AI Agent Global Connectivity tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.