create_fieldset · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What create_fieldset does on Dynatrace SaaS MCP Server

AI agents use create_fieldset to create or update resources in Dynatrace SaaS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dynatrace SaaS MCP Server environment.

WHY IT NEEDS A POLICY

Why create_fieldset needs a policy

This tool creates a new Grail fieldset, which is a reversible modification to Dynatrace's data storage configuration. It does not delete data (Destructive), execute arbitrary code (Execute), commit financial obligations (Financial), or read-only access (Read). Creating fieldsets could affect data organization and storage policies, hence medium severity due to potential operational impact if misconfigured by an agent.

From the tool's definition Tool name is 'create_fieldset' and description explicitly states 'Create a new Grail fieldset (WRITE, Storage Fieldsets v1)'. The description tags it as WRITE operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_fieldset Rate-limited

create_fieldset stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_fieldset": {
      "limits": [
        {
          "counter": "create_fieldset_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dynatrace SaaS MCP Server, so you can run agents against it safely.

FAQ

Questions about create_fieldset

What does the create_fieldset tool do? +

Create a new Grail fieldset (WRITE, Storage Fieldsets v1). It is categorised as a Write tool in the Dynatrace SaaS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_fieldset? +

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

create_fieldset is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_fieldset? +

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

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

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