List available data sources. This is typically the FIRST interactive step in data analysis. Ask user to provide a search term to filter the sources. 🔄 Auto-Cached: apiUrl and jwtToken are automatically provided from your authentication session. Only provide
AI agents call list_sources to retrieve information from Insight Digger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries a list of available data sources without side effects. It supports filtering via search terms but performs no creation, modification, deletion, or code execution. The automatic caching of authentication credentials does not change the fundamental read-only nature of the operation. This is a classic Read category operation used for data discovery and exploration.
From the tool's definition Tool name is 'list_sources' and description states 'List available data sources' with no mention of modification, deletion, or execution capabilities. The description emphasizes it is 'the FIRST interactive step in data analysis' for discovery purposes.
Attacks that exploit this kind of access
List available data sources. This is typically the FIRST interactive step in data analysis. Ask user to provide a search term to filter the sources. 🔄 Auto-Cached: apiUrl and jwtToken are automatically provided from your authentication session. Only provide. It is categorised as a Read tool in the Insight Digger MCP MCP Server, which means it retrieves data without modifying state.
Register the Insight Digger MCP server in PolicyLayer and add a rule for list_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 Insight Digger MCP. Nothing to install.
list_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_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_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_sources is provided by the Insight Digger MCP server (sandsiv/data_narrator_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 →