get_feature_project

Get a Feature Management project by key (Dynatrace Feature Management API).

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

What get_feature_project does on Dynatrace SaaS MCP Server

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

This tool retrieves feature project information by key from Dynatrace Feature Management API. The verb 'get' combined with the read-only nature of fetching project data by identifier confirms this is a Read operation. There is no data modification, deletion, or external execution. The blast radius is minimal since it only exposes observability and configuration metadata already within the Dynatrace system.

From the tool's definition Tool name 'get_feature_project' and description 'Get a Feature Management project by key' indicate retrieval of project metadata without modification or side effects.

Questions about get_feature_project

What does the get_feature_project tool do? +

Get a Feature Management project by key (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.

How do I enforce a policy on get_feature_project? +

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

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

Can I rate-limit get_feature_project? +

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

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

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