Medium Risk

set_subscriber_traffic_restrictions

Use this to enable or disable individual traffic types for a subscriber: mobile data, voice calls (mobile-originated and mobile-terminated), and SMS. Omit any flag to leave it unchanged. Changes take effect immediately at the OCS level. Params: iccid (subscriber identifier), dataAllowed (boolean,...

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

set_subscriber_traffic_restrictions can modify Carrier MCP: Give Your AI Agent Global Connectivity data, 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 use set_subscriber_traffic_restrictions to create or modify resources in Carrier MCP: Give Your AI Agent Global Connectivity. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call set_subscriber_traffic_restrictions repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Carrier MCP: Give Your AI Agent Global Connectivity.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_subscriber_traffic_restrictions": {
      "limits": [
        {
          "counter": "set_subscriber_traffic_restrictions_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 set_subscriber_traffic_restrictions 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 set_subscriber_traffic_restrictions only ever does what you allow.

SECURE CARRIER MCP: GIVE YOUR AI AGENT GLOBAL CONNECTIVITY →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the set_subscriber_traffic_restrictions tool do? +

Use this to enable or disable individual traffic types for a subscriber: mobile data, voice calls (mobile-originated and mobile-terminated), and SMS. Omit any flag to leave it unchanged. Changes take effect immediately at the OCS level. Params: iccid (subscriber identifier), dataAllowed (boolean, controls data traffic), mocAllowed (boolean, controls outbound calls), mtcAllowed (boolean, controls inbound calls), smsMoAllowed (boolean, controls outbound SMS). Returns: updated traffic restriction record for the subscriber. Do NOT use this to throttle bandwidth — use hlr_set_bitrate for speed limiting. Do NOT use this to suspend the subscriber entirely — use modify_subscriber_status (SUSPENDED) instead.. It is categorised as a Write tool in the Carrier MCP: Give Your AI Agent Global Connectivity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_subscriber_traffic_restrictions? +

Register the Carrier MCP: Give Your AI Agent Global Connectivity MCP server in PolicyLayer and add a rule for set_subscriber_traffic_restrictions: 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 set_subscriber_traffic_restrictions? +

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

Can I rate-limit set_subscriber_traffic_restrictions? +

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

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

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