Use this to retrieve timestamped network events for a subscriber: attach, detach, location updates, and handovers between operators. Useful for connectivity troubleshooting, roaming activity verification, and fraud pattern detection. Max 7 days per query. Params: iccid (subscriber identifier), st...
Part of the Carrier MCP: Give Your AI Agent Global Connectivity server.
Free to start. No card required.
AI agents invoke subscriber_network_events to trigger processes or run actions in Carrier MCP: Give Your AI Agent Global Connectivity. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
subscriber_network_events can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"subscriber_network_events": {
"limits": [
{
"counter": "subscriber_network_events_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Carrier MCP: Give Your AI Agent Global Connectivity policy for all 65 tools.
These attack patterns abuse exactly the kind of access subscriber_network_events gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Use this to retrieve timestamped network events for a subscriber: attach, detach, location updates, and handovers between operators. Useful for connectivity troubleshooting, roaming activity verification, and fraud pattern detection. Max 7 days per query. Params: iccid (subscriber identifier), startDate (YYYY-MM-DD, inclusive), endDate (YYYY-MM-DD, inclusive, max 7 days from start). Returns: array of event records with timestamp, eventType, country, operator, mccMnc. Do NOT use this for daily usage volumes — use subscriber_usage for data/voice/SMS byte counts. For real-time events (last 24h), prefer list_recent_ocs_events which reads from the ring buffer.. It is categorised as a Execute tool in the Carrier MCP: Give Your AI Agent Global Connectivity MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Carrier MCP: Give Your AI Agent Global Connectivity MCP server in PolicyLayer and add a rule for subscriber_network_events: 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.
subscriber_network_events is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the subscriber_network_events 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 subscriber_network_events. 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.
subscriber_network_events 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.
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.