sendEvent · Omnisend MCP Server MCP: Risk & Policy

WHAT IT DOES

What sendEvent does on Omnisend MCP Server

AI agents invoke sendEvent to trigger actions in Omnisend MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why sendEvent needs a policy

Sending an event triggers external operations in the Omnisend platform, specifically firing automations that can have downstream effects (emails, SMS, workflows). This is not a simple write of data—it actively triggers automated processes whose effects depend on the event type and arguments, making it Execute. Misuse could spam customers or trigger unintended marketing automations at scale, hence high severity.

From the tool's definition 'Send a customer event to Omnisend. Events are used to track customer behavior and can trigger automations.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sendEvent Rate-limited

sendEvent stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sendEvent": {
      "limits": [
        {
          "counter": "sendevent_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Omnisend MCP Server, so you can run agents against it safely.

FAQ

Questions about sendEvent

What does the sendEvent tool do? +

Send a customer event to Omnisend. Events are used to track customer behavior and can trigger automations. Can be custom events or predefined system events. It is categorised as a Execute tool in the Omnisend MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on sendEvent? +

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

What risk level is sendEvent? +

sendEvent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sendEvent? +

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

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

sendEvent is provided by the Omnisend MCP Server MCP server (plutzilla/omnisend-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.