Get counters of incidents per status for CIs from a given starting point.
AI agents call get_linked_cis_counters to retrieve information from InvGate Service Desk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves aggregated incident counter data associated with Configuration Items (CIs). It performs no data creation, modification, deletion, code execution, or financial operations. The function is purely informational—fetching statistics about incidents grouped by status. This is a straightforward Read category operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get_linked_cis_counters' and description 'Get counters of incidents per status for CIs from a given starting point' indicate a retrieval/query operation.
Attacks that exploit this kind of access
Get counters of incidents per status for CIs from a given starting point. It is categorised as a Read tool in the InvGate Service Desk MCP Server, which means it retrieves data without modifying state.
Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for get_linked_cis_counters: 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 InvGate Service Desk. Nothing to install.
get_linked_cis_counters 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 get_linked_cis_counters 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 get_linked_cis_counters. 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.
get_linked_cis_counters is provided by the InvGate Service Desk MCP server (oci:ghcr.io/tracegazer/invgate-service-desk-mcp:0.2.0). 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 →