update_trust_policy · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What update_trust_policy does on Dynatrace SaaS MCP Server

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

This tool modifies IAM trust policies, which are security-critical configuration. While reversible (Write rather than Destructive), misuse could grant unauthorized access to Dynatrace resources or compromise workload authentication chains. The high severity reflects that trust policy changes affect authentication boundaries and could enable privilege escalation if modified maliciously.

From the tool's definition Tool description explicitly states 'Update a WIF trust policy by UUID' and marks it as 'WRITE'. WIF (Workload Identity Federation) trust policies control authentication and authorization for service accounts and automated systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_trust_policy Rate-limited

update_trust_policy 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_trust_policy": {
      "limits": [
        {
          "counter": "update_trust_policy_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_trust_policy

What does the update_trust_policy tool do? +

Update a WIF trust policy by UUID (IAM v1, 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_trust_policy? +

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

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

Can I rate-limit update_trust_policy? +

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

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

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