event_create · ServiceNow MCP Server MCP: Risk & Policy

WHAT IT DOES

What event_create does on ServiceNow MCP Server

AI agents invoke event_create to trigger actions in ServiceNow 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 event_create needs a policy

Creating/firing a system event in ServiceNow triggers downstream workflows, business rules, and automated processes. This is an Execute-category action because the effects depend on which event is fired and can cascade across the system. Severity is high because a misused event could trigger unintended automated processes, approvals, notifications, or integrations at scale.

From the tool's definition 'Create/fire a system event' — firing a system event triggers external operations and workflows within ServiceNow

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

event_create Rate-limited

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

FAQ

Questions about event_create

What does the event_create tool do? +

Create/fire a system event. It is categorised as a Execute tool in the ServiceNow 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 event_create? +

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

What risk level is event_create? +

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

Can I rate-limit event_create? +

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

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

event_create is provided by the ServiceNow MCP Server MCP server (schwarztim/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.