Get a feature by key within a project (Dynatrace Feature Management API).
AI agents call get_feature 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 feature configuration data by key from Dynatrace Feature Management. It has no side effects—it only queries and returns existing data. The blast radius is minimal as an AI agent cannot cause harm by retrieving feature metadata. This falls squarely into the Read category.
From the tool's definition Tool name 'get_feature' and description 'Get a feature by key within a project' indicate a retrieval operation. The verb 'Get' and context of querying feature management data show no data modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get a feature by key within a project (Dynatrace Feature Management API). 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_feature: 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_feature 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_feature 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_feature. 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_feature 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 →