aos8_create_migration_run

A execute tool on the Hpe Networking MCP server.

SERVERHpe Networking SOURCEsecure-ssid/hpe-networking-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hpe-networking-mcp/aos8-create-migration-run.md

WHAT IT DOES

What aos8_create_migration_run does on Hpe Networking

AI agents invoke aos8_create_migration_run to trigger actions in Hpe Networking. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why aos8_create_migration_run is rated High

The name 'aos8_create_migration_run' strongly implies initiating a migration run for AOS8 devices, which is an Execute-level action — it triggers an operational workflow that can affect network device configuration and state. Sibling tools like aos8_apply_migration_run and aos8_execute_migration_rollback confirm this is part of a multi-step migration process.

From the tool's definition Tool name: aos8_create_migration_run; description is empty. Sibling tools include aos8_apply_migration_run, aos8_execute_migration_rollback, aos8_export_all, suggesting this is part of a migration workflow.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs aos8_create_migration_run safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hpe Networking, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For aos8_create_migration_run, this is the rule to start with:

aos8_create_migration_run Rate-limited

aos8_create_migration_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "aos8_create_migration_run": {
      "limits": [
        {
          "counter": "aos8_create_migration_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hpe Networking, apply this rule, and every aos8_create_migration_run call is checked against it from then on.

FAQ

Questions about aos8_create_migration_run

What does the aos8_create_migration_run tool do? +

aos8_create_migration_run is a execute tool on the Hpe Networking MCP server. It is categorised as a Execute tool in the Hpe Networking MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on aos8_create_migration_run? +

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

What risk level is aos8_create_migration_run? +

aos8_create_migration_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit aos8_create_migration_run? +

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

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

aos8_create_migration_run is provided by the Hpe Networking MCP server (secure-ssid/hpe-networking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hpe Networking, and thousands of servers like it.

This server

All 595 Hpe Networking tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP →diagram_create on Templonix Lite MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →