Low Risk

get_indexes_and_sourcetypes

Get a list of all indexes and their sourcetypes. This endpoint performs a search to gather: - All available indexes - All sourcetypes within each index - Event counts for each sourcetype - Time range information Returns: Dict[str, Any]: Dictionary containing: - indexes: List of all accessible ind...

How to control get_indexes_and_sourcetypes ↓

What get_indexes_and_sourcetypes does on Splunk

AI agents call get_indexes_and_sourcetypes to retrieve information from Splunk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_indexes_and_sourcetypes needs a policy

This tool retrieves and queries data from Splunk without any side effects. It gathers metadata about indexes and sourcetypes through a search operation and returns information only. No creation, modification, deletion, code execution, or financial operations are involved. The blast radius of misuse is minimal as it only exposes existing metadata that an authenticated user would typically have access to in Splunk.

From the tool's definition Tool description states it 'Get a list of all indexes and their sourcetypes' and 'performs a search to gather' information about indexes, sourcetypes, event counts, and time ranges.

Documented attack patterns abuse exactly the kind of access get_indexes_and_sourcetypes gives an agent:

How to control get_indexes_and_sourcetypes

PolicyLayer is an MCP gateway — it sits between your AI agents and Splunk, and nothing reaches the server without passing your rules. This is the rule we recommend for get_indexes_and_sourcetypes:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_indexes_and_sourcetypes": {}
  }
}

get_indexes_and_sourcetypes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Splunk — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_indexes_and_sourcetypes

What does the get_indexes_and_sourcetypes tool do? +

Get a list of all indexes and their sourcetypes. This endpoint performs a search to gather: - All available indexes - All sourcetypes within each index - Event counts for each sourcetype - Time range information Returns: Dict[str, Any]: Dictionary containing: - indexes: List of all accessible indexes - sourcetypes: Dictionary mapping indexes to their sourcetypes - metadata: Additional information about the search. It is categorised as a Read tool in the Splunk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_indexes_and_sourcetypes? +

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

What risk level is get_indexes_and_sourcetypes? +

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

Can I rate-limit get_indexes_and_sourcetypes? +

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

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

get_indexes_and_sourcetypes is provided by the Splunk MCP server (livehybrid/splunk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Splunk tool call.

Start from Splunk, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

12 Splunk tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.