list_incidents_by_helpdesk

List open incidents in a help desk (or several help desk IDs).

Server InvGate Service Desk oci:ghcr.io/tracegazer/invgate-service-desk-mcp:0.2.0
Category Read
Risk class Low
Parameters 00 required

What list_incidents_by_helpdesk does on InvGate Service Desk

AI agents call list_incidents_by_helpdesk 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.

Why list_incidents_by_helpdesk needs a policy

This tool retrieves and displays existing incident data. It performs no creation, modification, deletion, or external execution. The blast radius of an AI agent misusing this tool is minimal — it can only return incident information already accessible to the authenticated user, with no capability to change system state or access sensitive financial data beyond incident metadata.

From the tool's definition Tool name contains 'list' and description states 'List open incidents' — a query operation that retrieves data without side effects. The parameters are filter criteria (helpdesk IDs), not actions that modify or delete data.

Questions about list_incidents_by_helpdesk

What does the list_incidents_by_helpdesk tool do? +

List open incidents in a help desk (or several help desk IDs). It is categorised as a Read tool in the InvGate Service Desk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_incidents_by_helpdesk? +

Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for list_incidents_by_helpdesk: 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.

What risk level is list_incidents_by_helpdesk? +

list_incidents_by_helpdesk is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_incidents_by_helpdesk? +

Yes. Add a rate_limit block to the list_incidents_by_helpdesk 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.

How do I block list_incidents_by_helpdesk completely? +

Set action: deny in the PolicyLayer policy for list_incidents_by_helpdesk. 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.

What MCP server provides list_incidents_by_helpdesk? +

list_incidents_by_helpdesk 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.