AI agents call sigsci_get_request 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 details about a specific request—a query operation with no side effects. It cannot modify, delete, or execute operations. The 'read-only' characterization of the server tools further confirms this is a Read category tool. Even if the request details contain sensitive information, retrieval itself is non-destructive and causes no changes to the underlying system.
From the tool's definition Tool is described as 'Get details of a specific request by ID', which is a data retrieval operation. The server description emphasizes '40+ read-only tools for managing corporations and sites', and this tool is consistent with that pattern.
Attacks that exploit this kind of access
Get details of a specific request by ID. 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_request: 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_request 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_request 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_request. 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_request 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 →