Add a user to an organisational level (IAM v1, WRITE).
AI agents use add_iam_user 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.
This tool creates/modifies IAM user records at the organizational level, which is a reversible write operation but with significant blast radius. Unauthorized user addition could grant unwanted access to systems, escalate privileges, or create backdoors. However, it is not irreversible (users can be removed), not financial, and not code execution.
From the tool's definition Tool description explicitly states 'Add a user to an organisational level (IAM v1, WRITE)' – the WRITE designation and user-management action indicate data modification at organizational scope.
Attacks that exploit this kind of access
Add a user to an organisational level (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.
Register the Dynatrace SaaS MCP Server MCP server in PolicyLayer and add a rule for add_iam_user: 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.
add_iam_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_iam_user 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 add_iam_user. 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.
add_iam_user 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 →