update_self_notification · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What update_self_notification does on Dynatrace SaaS MCP Server

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

The tool creates or modifies data reversibly by updating an existing self-notification configuration. This is a Write operation rather than Read (it changes state), Execute (it doesn't trigger external operations or run code), Destructive (updates are reversible), or Financial (no money moves).

From the tool's definition Tool description explicitly states 'Update' and marks it as 'WRITE'. The tool modifies notification settings by ID, which is a reversible change (the previous notification configuration can be restored).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_self_notification Rate-limited

update_self_notification 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": {
    "update_self_notification": {
      "limits": [
        {
          "counter": "update_self_notification_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 update_self_notification

What does the update_self_notification tool do? +

Update a self-notification by ID (WRITE, platform notification v1). 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 update_self_notification? +

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

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

Can I rate-limit update_self_notification? +

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

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

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