get_indicator_result

Get full details of a single Indicator Result by sys_id.

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp

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/tedorigawa001-servicenow-mcp/get-indicator-result.md

WHAT IT DOES

What get_indicator_result does on ServiceNow-MCP

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

RISK

Why get_indicator_result is rated Low

This tool retrieves and queries indicator result data from ServiceNow by identifier. It performs a read-only operation with no side effects, data modification, code execution, or destructive capability. The low severity reflects minimal blast radius even if misused by an agent—querying indicator results cannot damage systems or create unintended changes.

From the tool's definition Tool name 'get_indicator_result' and description 'Get full details of a single Indicator Result by sys_id' indicates a retrieval operation with the verb 'Get' and no modification or deletion language.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_indicator_result safely

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

get_indicator_result Allowed

get_indicator_result 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": {
    "get_indicator_result": {}
  }
}

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

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

FAQ

Questions about get_indicator_result

What does the get_indicator_result tool do? +

Get full details of a single Indicator Result by sys_id. It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_indicator_result? +

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

What risk level is get_indicator_result? +

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

Can I rate-limit get_indicator_result? +

Yes. Add a rate_limit block to the get_indicator_result 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 get_indicator_result completely? +

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

get_indicator_result is provided by the ServiceNow MCP server (tedorigawa001/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ServiceNow, and thousands of servers like it.

This server

All 495 ServiceNow tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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