List Import Set data source definitions (file/JDBC/REST loaders)
AI agents call list_data_sources to retrieve information from ServiceNow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists metadata about data source definitions (file, JDBC, REST loaders) in ServiceNow's Import Set system. It queries existing configurations without creating, modifying, deleting, or triggering any operations. The action is purely informational and read-only, posing minimal risk even if invoked by an AI agent with incorrect context.
From the tool's definition Tool name 'list_data_sources' and description 'List Import Set data source definitions' indicate a query/retrieval operation with no modification or execution of external systems.
Attacks that exploit this kind of access
List Import Set data source definitions (file/JDBC/REST loaders). It is categorised as a Read tool in the ServiceNow-MCP MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for list_data_sources: 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.
list_data_sources 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 list_data_sources 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 list_data_sources. 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.
list_data_sources 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.
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 →