List incidents for the authenticated organization. Filter by status (OPEN/RESOLVED), monitor id, or paginate.
AI agents call vs_incidents_list to retrieve information from Visual Sentinel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries incident data with optional filters (status, monitor ID) and pagination—classic Read operation characteristics. While it requires authentication via API key, it performs no destructive actions, does not execute code, and does not modify data. The blast radius of misuse is limited to information disclosure about incidents within the organization.
From the tool's definition Tool name 'vs_incidents_list' and description 'List incidents for the authenticated organization' indicate a retrieval operation with filtering and pagination capabilities. No data modification, deletion, or side effects are described.
Attacks that exploit this kind of access
List incidents for the authenticated organization. Filter by status (OPEN/RESOLVED), monitor id, or paginate. It is categorised as a Read tool in the Visual Sentinel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Visual Sentinel MCP Server MCP server in PolicyLayer and add a rule for vs_incidents_list: 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 Visual Sentinel MCP Server. Nothing to install.
vs_incidents_list 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 vs_incidents_list 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 vs_incidents_list. 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.
vs_incidents_list is provided by the Visual Sentinel MCP Server MCP server (visualsentinel/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 →