List all OpenPipeline configurations (one per data type: logs, events, bizevents,
AI agents call list_openpipeline_configurations 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 observability pipeline configurations for inspection purposes. It has no side effects, does not modify data, and does not execute commands or delete resources. The blast radius of misuse is minimal—an agent querying configurations cannot cause damage to the system or data. This is a standard read/query operation.
From the tool's definition Tool name 'list_openpipeline_configurations' and description indicate it lists/retrieves OpenPipeline configurations without modification. The verb 'list' is a read-only operation that queries existing data.
Attacks that exploit this kind of access
List all OpenPipeline configurations (one per data type: logs, events, bizevents,. 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_openpipeline_configurations: 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_openpipeline_configurations 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_openpipeline_configurations 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_openpipeline_configurations. 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_openpipeline_configurations 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 →