create_trust_policy_mapping · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What create_trust_policy_mapping does on Dynatrace SaaS MCP Server

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

This tool creates IAM trust policy mappings, which are configuration changes that can be reversed (updated or deleted later). It is not destructive (no permanent deletion) and not financial (no money movement). It is a Write operation because it creates/modifies identity configuration state.

From the tool's definition Tool description explicitly states 'Create a WIF service user mapping' and tags it as 'WRITE'. WIF (Workload Identity Federation) mappings are identity and access control configurations that establish trust relationships between external identity providers…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_trust_policy_mapping Rate-limited

create_trust_policy_mapping 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": {
    "create_trust_policy_mapping": {
      "limits": [
        {
          "counter": "create_trust_policy_mapping_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 create_trust_policy_mapping

What does the create_trust_policy_mapping tool do? +

Create a WIF service user mapping for a trust policy (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 create_trust_policy_mapping? +

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

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

Can I rate-limit create_trust_policy_mapping? +

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

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

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