list_servicenow_incidents

List or search incidents in ServiceNow.

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/freshdesk/list-servicenow-incidents.md

WHAT IT DOES

What list_servicenow_incidents does on Freshdesk

AI agents call list_servicenow_incidents to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_servicenow_incidents is rated Low

This tool retrieves or searches for incident data from ServiceNow without creating, modifying, deleting, or executing any actions. It is a straightforward read operation with minimal risk, as it only queries existing data and presents results to the user.

From the tool's definition Tool name 'list_servicenow_incidents' and description 'List or search incidents in ServiceNow' indicate retrieval and querying operations with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_servicenow_incidents safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_servicenow_incidents, this is the rule to start with:

list_servicenow_incidents Allowed

list_servicenow_incidents is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_servicenow_incidents": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every list_servicenow_incidents call is checked against it from then on.

FAQ

Questions about list_servicenow_incidents

What does the list_servicenow_incidents tool do? +

List or search incidents in ServiceNow. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_servicenow_incidents? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for list_servicenow_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 Freshdesk. Nothing to install.

What risk level is list_servicenow_incidents? +

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

Can I rate-limit list_servicenow_incidents? +

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

How do I block list_servicenow_incidents completely? +

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

What MCP server provides list_servicenow_incidents? +

list_servicenow_incidents is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Freshdesk, and thousands of servers like it.

This server

All 422 Freshdesk tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →