AI agents call sigsci_list_cloudwaf_instances to retrieve information from Sigsci 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 CloudWAF instances belonging to a corporation. It performs no modifications, deletions, or external operations. While the enumeration of security infrastructure could inform a reconnaissance attack, the tool itself is purely informational and read-only, making it a Read category risk.
From the tool's definition Tool name 'list' and description 'List all CloudWAF instances' indicate data retrieval with no side effects. The server description confirms '40+ read-only tools' and the sibling tools (sigsci_get_*, sigsci_list_*) all follow read-only query patterns.
Attacks that exploit this kind of access
List all CloudWAF instances in a corporation. It is categorised as a Read tool in the Sigsci MCP Server, which means it retrieves data without modifying state.
Register the Sigsci MCP server in PolicyLayer and add a rule for sigsci_list_cloudwaf_instances: 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 Sigsci. Nothing to install.
sigsci_list_cloudwaf_instances 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 sigsci_list_cloudwaf_instances 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 sigsci_list_cloudwaf_instances. 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.
sigsci_list_cloudwaf_instances is provided by the Sigsci MCP server (yuki777/sigsci-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 →