upload_lookup_data · Dynatrace SaaS MCP Server MCP

WHAT IT DOES

What upload_lookup_data does on Dynatrace SaaS MCP Server

AI agents use upload_lookup_data 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 upload_lookup_data needs a policy

This tool creates or modifies data in a lookup store without permanently destroying it. While 'upload' could imply file operations, the context clarifies it writes/stores data in Dynatrace's Grail Resource Store. This is a Write operation: data modification that is reversible and not destructive.

From the tool's definition Tool name contains 'upload' and description explicitly states 'WRITE' and 'Upload tabular lookup data into the Grail Resource Store'. The action is reversible (data can be updated or deleted later).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload_lookup_data Rate-limited

upload_lookup_data 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": {
    "upload_lookup_data": {
      "limits": [
        {
          "counter": "upload_lookup_data_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 upload_lookup_data

What does the upload_lookup_data tool do? +

Upload tabular lookup data into the Grail Resource Store (WRITE, Resource Store v1) for use with the. 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 upload_lookup_data? +

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

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

Can I rate-limit upload_lookup_data? +

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

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

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