import_migration | PolicyLayer

WHAT IT DOES

What import_migration does on Cloudera Data Visualization MCP Server

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

WHY IT NEEDS A POLICY

Why import_migration needs a policy

The import_migration tool creates or modifies system state by ingesting a migration bundle, which constitutes a Write operation. It ranks as high severity because importing a migration bundle could introduce significant unintended changes across multiple resources (groups, users, roles, segments, workspaces, datasets, visuals, connections) if the bundle contents are malicious or incorrect.

From the tool's definition Tool performs 'import' of a 'migration bundle' which modifies Cloudera Data Visualization resources by loading external data/configurations into the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_migration Rate-limited

import_migration 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": {
    "import_migration": {
      "limits": [
        {
          "counter": "import_migration_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 Cloudera Data Visualization MCP Server, so you can run agents against it safely.

FAQ

Questions about import_migration

What does the import_migration tool do? +

Import a CDV migration bundle. It is categorised as a Write tool in the Cloudera Data Visualization 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 import_migration? +

Register the Cloudera Data Visualization MCP Server MCP server in PolicyLayer and add a rule for import_migration: 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 Cloudera Data Visualization MCP Server. Nothing to install.

What risk level is import_migration? +

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

Can I rate-limit import_migration? +

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

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

import_migration is provided by the Cloudera Data Visualization MCP Server MCP server (kevintalbert/cdv-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.