ingest_events · Dynatrace SaaS MCP Server MCP: Risk & Policy

WHAT IT DOES

What ingest_events does on Dynatrace SaaS MCP Server

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

WHY IT NEEDS A POLICY

Why ingest_events needs a policy

Ingesting events is a write operation that creates new data in Dynatrace but does not irreversibly delete or modify existing data, nor does it execute arbitrary code or move money.

From the tool's definition Tool explicitly described as 'Ingest a custom event into Dynatrace via POST /api/v2/events/ingest (WRITE)'. Uses POST HTTP method and is labeled as a write operation. Creates new event records in the Dynatrace system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ingest_events Rate-limited

ingest_events 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": {
    "ingest_events": {
      "limits": [
        {
          "counter": "ingest_events_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 Dynatrace SaaS MCP Server, so you can run agents against it safely.

FAQ

Questions about ingest_events

What does the ingest_events tool do? +

Ingest a custom event into Dynatrace via POST /api/v2/events/ingest (WRITE). It is categorised as a Write tool in the Dynatrace SaaS 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 ingest_events? +

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

What risk level is ingest_events? +

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

Can I rate-limit ingest_events? +

Yes. Add a rate_limit block to the ingest_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.

How do I block ingest_events completely? +

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

What MCP server provides ingest_events? +

ingest_events is provided by the Dynatrace SaaS MCP Server MCP server (mnmozi/dynatrace-mcp-saas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.