Checks whether a specific IP is present in the ip_list of a zone.
AI agents call zone_has_ip 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 queries zone IP membership status without creating, modifying, deleting, or executing any operations. It is a pure read operation similar to other Read tools on the server like 'get_zone_status' and 'get_system_health'. The blast radius of misuse is minimal—an agent could only learn which IPs exist in zones, with no ability to alter configurations or trigger actions.
From the tool's definition Tool name 'zone_has_ip' and description 'Checks whether a specific IP is present in the ip_list of a zone' indicate a query/lookup operation with no side effects.
Attacks that exploit this kind of access
Checks whether a specific IP is present in the ip_list of a zone. 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 zone_has_ip: 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.
zone_has_ip 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 zone_has_ip 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 zone_has_ip. 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.
zone_has_ip 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 →