List open incidents in the process engine. Filter by processInstanceId or incidentType (\
AI agents call list_incidents to retrieve information from CIB Seven 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 from the process engine without modifying, deleting, or executing any operations. It supports filtering by processInstanceId or incidentType but only returns information. No side effects or state changes occur. This is a straightforward Read operation with low risk.
From the tool's definition Tool name 'list_incidents' and description 'List open incidents in the process engine. Filter by processInstanceId or incidentType' indicate a query/listing operation with filtering capabilities.
Attacks that exploit this kind of access
List open incidents in the process engine. Filter by processInstanceId or incidentType (\. It is categorised as a Read tool in the CIB Seven MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CIB Seven MCP Server MCP server in PolicyLayer and add a rule for list_incidents: 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 CIB Seven MCP Server. Nothing to install.
list_incidents 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 list_incidents 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 list_incidents. 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.
list_incidents is provided by the CIB Seven MCP Server MCP server (krixerx/cib7-mcp). 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 →