List WIF service user mappings for a trust policy (IAM v1).
AI agents call list_trust_policy_mappings to retrieve information from Dynatrace SaaS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing IAM configuration data without creating, modifying, or deleting resources. While trust policy information is security-sensitive, reading it poses minimal risk compared to modification or deletion. The blast radius of misuse is limited to information disclosure of IAM mappings already configured in Dynatrace.
From the tool's definition Tool name 'list_trust_policy_mappings' and description 'List WIF service user mappings for a trust policy' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List WIF service user mappings for a trust policy (IAM v1). It is categorised as a Read tool in the Dynatrace SaaS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for list_trust_policy_mappings: 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.
list_trust_policy_mappings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_trust_policy_mappings 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.
Set action: deny in the PolicyLayer policy for list_trust_policy_mappings. 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.
list_trust_policy_mappings 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →