list_synthetic_locations

List all synthetic locations (both public and private) available for the environment.

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

What list_synthetic_locations does on Dynatrace SaaS MCP Server

AI agents call list_synthetic_locations 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 list_synthetic_locations needs a policy

This tool retrieves configuration metadata about available synthetic monitoring locations. It performs a simple enumeration/query of existing resources with no capability to modify, delete, execute, or commit financial transactions. The blast radius of misuse is minimal—an attacker could only discover what synthetic locations are configured, which is non-sensitive operational metadata in an observability context.

From the tool's definition Tool name 'list_synthetic_locations' and description 'List all synthetic locations' indicate a retrieval operation with no side effects. Matches the Read category pattern of 'list' operations that query data without modification.

Questions about list_synthetic_locations

What does the list_synthetic_locations tool do? +

List all synthetic locations (both public and private) available for the environment. 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 list_synthetic_locations? +

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

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

Can I rate-limit list_synthetic_locations? +

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

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

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