get_servicenow_incident
Get a single incident by number (e.g., INC0010001) or sys_id.
This record as markdown: /tools/freshdesk/get-servicenow-incident.md
What get_servicenow_incident does on Freshdesk
AI agents call get_servicenow_incident 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.
Why get_servicenow_incident is rated Low
This tool retrieves incident data without side effects. It is a read-only query operation that returns information about a single incident. No data is created, modified, deleted, or any external operations triggered. The blast radius of misuse is minimal—an agent could only access and view incident details it may not be authorized to see, a typical confidentiality risk rather than integrity or availability risk.
From the tool's definition Tool description explicitly states 'Get a single incident' — a retrieval operation with no modification, deletion, or execution of external actions. It queries ServiceNow by incident number or sys_id.
Attacks that exploit this kind of access
The rule that runs get_servicenow_incident 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 get_servicenow_incident, this is the rule to start with:
get_servicenow_incident is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every get_servicenow_incident call is checked against it from then on.
Questions about get_servicenow_incident
Get a single incident by number (e.g., INC0010001) or sys_id. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for get_servicenow_incident: 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.
get_servicenow_incident 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_servicenow_incident 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_servicenow_incident. 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_servicenow_incident 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.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue