AI agents call sigsci_get_blacklist 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 blacklist data for a site without modifying, deleting, or executing any operations. It is a straightforward data retrieval operation consistent with the read-only nature of the Signal Sciences management API tools. The low severity reflects minimal risk from an AI agent invoking this tool—it only exposes existing security policy data.
From the tool's definition Tool name 'sigsci_get_blacklist' with description 'Get blacklist for a site' indicates a retrieval operation. The verb 'Get' and the server description stating '40+ read-only tools' confirm this is a read-only query with no side effects.
Attacks that exploit this kind of access
Get blacklist for a site. 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_get_blacklist: 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_get_blacklist 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_get_blacklist 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_get_blacklist. 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_get_blacklist 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 →