Medium Risk

update_subscription_by_token

Update a subscription identified by its channel type and token. Provide `subscription_type` and `token` to identify the subscription, then pass the fields to update in `subscription`.

Handles credentials or secrets (token)

Part of the OneSignal MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use update_subscription_by_token to create or modify resources in OneSignal. 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 update_subscription_by_token repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach OneSignal.

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

onesignal-onesignal.yaml
tools:
  update_subscription_by_token:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full OneSignal policy for all 31 tools.

Tool Name update_subscription_by_token
Category Write
Risk Level Medium

View all 31 tools →

Agents calling write-class tools like update_subscription_by_token have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the update_subscription_by_token tool do? +

Update a subscription identified by its channel type and token. Provide `subscription_type` and `token` to identify the subscription, then pass the fields to update in `subscription`.. It is categorised as a Write tool in the OneSignal 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_subscription_by_token? +

Add a rule in your Intercept YAML policy under the tools section for update_subscription_by_token. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the OneSignal MCP server.

What risk level is update_subscription_by_token? +

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

Can I rate-limit update_subscription_by_token? +

Yes. Add a rate_limit block to the update_subscription_by_token rule in your Intercept 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_subscription_by_token completely? +

Set action: deny in the Intercept policy for update_subscription_by_token. 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_subscription_by_token? +

update_subscription_by_token is provided by the OneSignal MCP server (onesignal/onesignal). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.