send_transactional_message · OneSignal MCP Server MCP

WHAT IT DOES

What send_transactional_message does on OneSignal MCP Server

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

WHY IT NEEDS A POLICY

Why send_transactional_message needs a policy

An AI agent can call send_transactional_message faster than any human can review — one bad instruction and it creates or modifies resources in OneSignal MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_transactional_message Rate-limited

send_transactional_message 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": {
    "send_transactional_message": {
      "limits": [
        {
          "counter": "send_transactional_message_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 OneSignal MCP Server, so you can run agents against it safely.

FAQ

Questions about send_transactional_message

What does the send_transactional_message tool do? +

Send a transactional message (immediate delivery). It is categorised as a Write tool in the OneSignal 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 send_transactional_message? +

Register the OneSignal MCP Server MCP server in PolicyLayer and add a rule for send_transactional_message: 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 OneSignal MCP Server. Nothing to install.

What risk level is send_transactional_message? +

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

Can I rate-limit send_transactional_message? +

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

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

send_transactional_message is provided by the OneSignal MCP Server MCP server (weirdbrains/onesignal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.