List incidents assigned to an agent (by id, email or username).
AI agents call list_incidents_by_agent 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 incident data filtered by agent assignment. It performs data lookup only, matching the Read category definition of retrieving or querying data with no side effects. The blast radius if misused is minimal—an agent could enumerate incidents assigned to a particular user, which is informational exposure at worst.
From the tool's definition Tool name includes 'list' and description states 'List incidents assigned to an agent' — a pure retrieval operation with no modification, deletion, or execution of side effects.
Attacks that exploit this kind of access
List incidents assigned to an agent (by id, email or username). 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 list_incidents_by_agent: 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.
list_incidents_by_agent 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_by_agent 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_by_agent. 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_by_agent 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 →