AI agents call sigsci_list_events 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 queries/retrieves event data for a site with no side effects or data modification. It follows the 'list' pattern characteristic of Read operations. The server's focus on read-only functionality and the absence of any modification, deletion, or execution capability confirms the Read category. Severity is low because retrieving event logs presents minimal blast radius even if accessed improperly.
From the tool's definition Tool name 'sigsci_list_events' with description 'List events for a site' indicates a retrieval operation. Server description emphasizes '40+ read-only tools', and all sibling tools shown (sigsci_get_*) are read operations that retrieve data without…
Attacks that exploit this kind of access
List events 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_list_events: 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_events 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_events 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_events. 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_events 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 →