List all saved searches in Splunk Returns: List of saved searches with their names, descriptions, and search queries
AI agents call list_saved_searches 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.
This tool queries and retrieves metadata about saved searches in Splunk without modifying, executing, or deleting any data. It is a pure read operation that lists existing resources. The low severity reflects minimal blast radius—disclosure of saved search names and queries could inform an attacker about monitoring patterns but does not directly compromise data integrity or enable destructive actions.
From the tool's definition Tool name 'list_saved_searches' and description 'List all saved searches in Splunk' with return value of 'names, descriptions, and search queries' indicates a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_saved_searches gives an agent:
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 list_saved_searches:
{
"version": "1",
"default": "deny",
"tools": {
"list_saved_searches": {}
}
}list_saved_searches is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all saved searches in Splunk Returns: List of saved searches with their names, descriptions, and search queries. It is categorised as a Read tool in the Splunk MCP Server, which means it retrieves data without modifying state.
Register the Splunk MCP server in PolicyLayer and add a rule for list_saved_searches: 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.
list_saved_searches 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_saved_searches 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_saved_searches. 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_saved_searches 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.
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.