Get a single Dynatrace Automation workflow execution by ID (platform Automation v1).
AI agents call get_workflow_execution 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 queries and retrieves data about a workflow execution by its identifier. It performs a read-only lookup operation that does not create, modify, delete, or execute any workflows. The verb 'Get' and the absence of any mutation or triggering language confirm this is a Read category tool with low severity, as it only exposes historical execution data without risk of unintended side effects.
From the tool's definition Tool name 'get_workflow_execution' and description 'Get a single Dynatrace Automation workflow execution by ID' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get a single Dynatrace Automation workflow execution by ID (platform Automation 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 get_workflow_execution: 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.
get_workflow_execution 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 get_workflow_execution 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 get_workflow_execution. 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.
get_workflow_execution 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 →