migration_export · CyPerf MCP Server MCP: Risk & Policy

WHAT IT DOES

What migration_export does on CyPerf MCP Server

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

WHY IT NEEDS A POLICY

Why migration_export needs a policy

This tool exports controller data, which is a reversible write operation—the export creates a data artifact but does not modify or delete the original controller state. It is not destructive (original data remains), not financial, and not a simple read (it performs an action with side effects: generating an export).

From the tool's definition Tool name is 'migration_export' and description states 'Export controller data for migration.' The action is exporting data, which is a write operation that creates an output artifact (exported data) for migration purposes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

migration_export Rate-limited

migration_export 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": {
    "migration_export": {
      "limits": [
        {
          "counter": "migration_export_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 CyPerf MCP Server, so you can run agents against it safely.

FAQ

Questions about migration_export

What does the migration_export tool do? +

[Migration] Export controller data for migration. It is categorised as a Write tool in the CyPerf 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 migration_export? +

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

What risk level is migration_export? +

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

Can I rate-limit migration_export? +

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

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

migration_export is provided by the CyPerf MCP Server MCP server (keysight/cyperf-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.