get_openpipeline_technology_processors

Get the processors available for a specific OpenPipeline technology.

Server Dynatrace SaaS MCP Server mnmozi/dynatrace-mcp-saas
Category Read
Risk class Low
Parameters 00 required

What get_openpipeline_technology_processors does on Dynatrace SaaS MCP Server

AI agents call get_openpipeline_technology_processors 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.

Why get_openpipeline_technology_processors needs a policy

This tool retrieves observability configuration data (available processors) from Dynatrace without side effects. It does not create, modify, delete, execute code, or move money. The blast radius of misuse is minimal—an agent could only retrieve processor information that is already available in the system. Classification as Read is appropriate.

From the tool's definition Tool description states 'Get the processors available' for OpenPipeline technology—a query operation that retrieves configuration metadata without modifying or executing anything.

Questions about get_openpipeline_technology_processors

What does the get_openpipeline_technology_processors tool do? +

Get the processors available for a specific OpenPipeline technology. It is categorised as a Read tool in the Dynatrace SaaS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_openpipeline_technology_processors? +

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

get_openpipeline_technology_processors is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_openpipeline_technology_processors? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.