update_dashboard · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What update_dashboard does on Dynatrace SaaS MCP Server

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

This tool creates or modifies data reversibly. Dashboard updates are configuration changes that can be undone by subsequent updates. The blast radius is moderate: an agent could misconfigure dashboards affecting visualization and alerting for other users, but data integrity and system stability are not compromised. Not Destructive (reversible), not Execute (no arbitrary code), not Financial.

From the tool's definition Tool name is 'update_dashboard' and description explicitly states '(WRITE)'. Updates modify existing dashboards without deleting them or creating irreversible changes—changes can be reverted by updating again.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_dashboard Rate-limited

update_dashboard 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_dashboard": {
      "limits": [
        {
          "counter": "update_dashboard_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_dashboard

What does the update_dashboard tool do? +

Update an existing dashboard (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 update_dashboard? +

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

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

Can I rate-limit update_dashboard? +

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

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

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