Get a specific ServiceNow incident by ID.
AI agents call get_incident to retrieve information from Enterprise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves incident data from ServiceNow without modifying, deleting, or executing any operations. It is a straightforward read operation that poses minimal security risk, though the sensitivity of the data returned (incident details) keeps it from being truly risk-free. Classified as Read/low because the operation is non-mutating and the blast radius of misuse is limited to information disclosure.
From the tool's definition Tool name is 'get_incident' and description states 'Get a specific ServiceNow incident by ID.' The verb 'get' and the retrieval-focused description indicate a query operation with no side effects.
Attacks that exploit this kind of access
Get a specific ServiceNow incident by ID. It is categorised as a Read tool in the Enterprise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enterprise MCP Server MCP server in PolicyLayer and add a rule for get_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 Enterprise MCP Server. Nothing to install.
get_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_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_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_incident is provided by the Enterprise MCP Server MCP server (maybeswapnil/enterprise-mcp). 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 →