Count historic process instances matching filters. Cheap — returns a number, no row fetch. Same filter surface as list_process_instances. For day/week/month histograms use process_instance_stats. See \
AI agents call count_process_instances 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 queries and aggregates process instance data without modifying, deleting, or executing operations. It accepts filter parameters to scope the count, but produces only a numeric result. This is a classic Read operation—safe for inspection and diagnosis of process instances as described in the server's purpose. No data is created, modified, deleted, or committed as a result of calling this tool.
From the tool's definition Tool description explicitly states it 'Count[s] historic process instances matching filters' and 'returns a number, no row fetch'. The verb 'count' and return type (a number, not data rows) confirm this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Count historic process instances matching filters. Cheap — returns a number, no row fetch. Same filter surface as list_process_instances. For day/week/month histograms use process_instance_stats. See \. 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 count_process_instances: 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.
count_process_instances 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 count_process_instances 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 count_process_instances. 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.
count_process_instances 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.
count_process_instances is one line of CIB Seven MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →