get_ci

A read tool on the ServiceNow MCP server.

SERVERServiceNow MCP Server SOURCEpypi:mcp-server-servicenow

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/io-github-jschuller-mcp-server-servicenow/get-ci.md

WHAT IT DOES

What get_ci does on ServiceNow MCP Server

AI agents call get_ci to retrieve information from ServiceNow MCP Server 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_ci is rated Low

Despite the empty description, the tool name and context strongly suggest this retrieves a Configuration Item from the CMDB without modification. Sibling tools named 'create_ci', 'delete_record', etc. show this server supports multiple patterns; 'get_ci' clearly maps to the Read category.

From the tool's definition Tool name 'get_ci' (get Configuration Item) combined with sibling tools like 'get_record', 'get_current_user', and 'get_table_schema' indicates this is a retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_ci safely

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

get_ci Allowed

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

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

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

FAQ

Questions about get_ci

What does the get_ci tool do? +

get_ci is a read tool on the ServiceNow MCP Server MCP server. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_ci? +

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

What risk level is get_ci? +

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

Can I rate-limit get_ci? +

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

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

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

KEEP EXPLORING

More on ServiceNow MCP Server, and thousands of servers like it.

This server

All 19 ServiceNow MCP Server 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 →