Adds an IP to the ip_list of a multi-IP zone. Idempotent: no-op if already present.
AI agents use add_ip_to_zone 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.
This tool creates or modifies DDoS mitigation zone data by adding IPs to allowlists or blocklists. While reversible (IPs can be removed), misconfiguration could result in legitimate traffic being blocked, denial of service impacts, or inadvertent exposure of protected systems.
From the tool's definition Adds an IP to the ip_list of a multi-IP zone. This modifies zone configuration data by appending to a list, which is a reversible write operation. The idempotent nature confirms it does not delete or destroy data.
Attacks that exploit this kind of access
Adds an IP to the ip_list of a multi-IP zone. Idempotent: no-op if already present. 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.
Register the A10 Guardian MCP server in PolicyLayer and add a rule for add_ip_to_zone: 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.
add_ip_to_zone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_ip_to_zone 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 add_ip_to_zone. 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.
add_ip_to_zone 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 →