import_zone_template · A10 Guardian MCP: Risk & Policy

WHAT IT DOES

What import_zone_template does on A10 Guardian

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

WHY IT NEEDS A POLICY

Why import_zone_template needs a policy

This tool creates or modifies DDoS mitigation configurations by importing zone templates. While not destructive (the import is reversible), it is a Write operation that changes device state. Severity is high because misconfigured DDoS templates could disrupt legitimate traffic or weaken security posture on critical infrastructure (A10 Guardian devices are enterprise security appliances).

From the tool's definition Tool name 'import_zone_template' and description 'Imports a template from an existing A10 zone configuration' indicates modification of DDoS mitigation device configuration by importing/loading a template into the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_zone_template Rate-limited

import_zone_template 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_zone_template": {
      "limits": [
        {
          "counter": "import_zone_template_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 A10 Guardian, so you can run agents against it safely.

FAQ

Questions about import_zone_template

What does the import_zone_template tool do? +

Imports a template from an existing A10 zone configuration. It is categorised as a Write tool in the A10 Guardian 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_zone_template? +

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

What risk level is import_zone_template? +

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

Can I rate-limit import_zone_template? +

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

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

import_zone_template is provided by the A10 Guardian MCP server (opastorello/a10-guardian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.