Checks if an IP address exists in any WAF IP Set (Blocklists/Allowlists).
AI agents call check_ip_in_waf to retrieve information from AWS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about whether an IP exists in WAF allowlists or blocklists—a pure query operation. It does not create, modify, delete, or execute anything; it only inspects existing security configuration data. The server's explicit 'read-only' design and audit logging further support this classification.
From the tool's definition Tool name 'check_ip_in_waf' and description 'Checks if an IP address exists in any WAF IP Set' indicate a query/lookup operation with no modification or side effects. The verb 'checks' and the read-only nature of IP Set queries align with the Read category.
Attacks that exploit this kind of access
Checks if an IP address exists in any WAF IP Set (Blocklists/Allowlists). It is categorised as a Read tool in the AWS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS MCP Server MCP server in PolicyLayer and add a rule for check_ip_in_waf: 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 AWS MCP Server. Nothing to install.
check_ip_in_waf 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 check_ip_in_waf 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 check_ip_in_waf. 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.
check_ip_in_waf is provided by the AWS MCP Server MCP server (sergiosediq/aws-mcp-server). 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 →