AI agents call sigsci_list_corp_rules 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 configuration data (rules) from a corporation in Signal Sciences/Fastly NGWAF. It performs read-only enumeration with no side effects. The blast radius is minimal—an AI agent misusing this tool could at worst enumerate rules it shouldn't see, but cannot modify, delete, or execute policies. Low severity is appropriate for information disclosure of administrative configuration.
From the tool's definition Tool name contains 'list' and description states 'List all rules in a corporation'. Server description explicitly notes '40+ read-only tools'. This is a query operation that retrieves rule data without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
List all rules 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_corp_rules: 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_corp_rules 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_corp_rules 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_corp_rules. 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_corp_rules 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 →