List Settings 2.0 objects, filtered by schema and/or scope. Returns one page; pass nextPageKey to page through results.
AI agents call list_settings_objects 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.
The tool retrieves settings configuration metadata from Dynatrace without modifying state. It supports filtering and pagination but performs no side effects. This is a standard Read operation with low risk even if an agent queries unintended scopes, as no data is altered or destroyed. Severity is low because listing configuration objects poses minimal harm compared to modifying or deleting them.
From the tool's definition Tool description states 'List Settings 2.0 objects' and 'Returns one page' — clearly a retrieval/query operation. No mutations, deletions, or external triggers described.
Attacks that exploit this kind of access
List Settings 2.0 objects, filtered by schema and/or scope. Returns one page; pass nextPageKey to page through results. 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_settings_objects: 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_settings_objects 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_settings_objects 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_settings_objects. 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_settings_objects 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 →