ingest_logs · Dynatrace SaaS MCP Server MCP: Risk & Policy

WHAT IT DOES

What ingest_logs does on Dynatrace SaaS MCP Server

AI agents use ingest_logs 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_logs needs a policy

The tool creates or modifies data (ingesting logs) in a reversible manner. While logs are typically append-only and cannot be truly 'updated', ingestion is fundamentally a write operation that adds new records. It does not delete or destroy data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).

From the tool's definition Tool description explicitly states "WRITE" and uses POST /api/v2/logs/ingest to ingest log records into Dynatrace. This creates new log data in the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ingest_logs Rate-limited

ingest_logs 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_logs": {
      "limits": [
        {
          "counter": "ingest_logs_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_logs

What does the ingest_logs tool do? +

Ingest one or more log records into Dynatrace via POST /api/v2/logs/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_logs? +

Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for ingest_logs: 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_logs? +

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

Can I rate-limit ingest_logs? +

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

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

ingest_logs 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.