Lists all available zone templates with their metadata.
AI agents call list_zone_templates to retrieve information from A10 Guardian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates zone templates without creating, modifying, deleting, or executing operations. It is a passive read operation that queries existing configuration metadata. The blast radius of misuse is minimal—an attacker could discover template names but cannot directly harm infrastructure or trigger DDoS mitigation actions.
From the tool's definition Tool name 'list_zone_templates' and description 'Lists all available zone templates with their metadata' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Lists all available zone templates with their metadata. It is categorised as a Read tool in the A10 Guardian MCP Server, which means it retrieves data without modifying state.
Register the A10 Guardian MCP server in PolicyLayer and add a rule for list_zone_templates: 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.
list_zone_templates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_zone_templates 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.
Set action: deny in the PolicyLayer policy for list_zone_templates. 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.
list_zone_templates 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →