List or retrieve saved searches from Splunk.
AI agents call list_saved_searches to retrieve information from Splunk MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing saved searches without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal blast radius—an AI agent misusing it could at worst enumerate saved searches to gather intelligence, but cannot alter system state or trigger destructive actions.
From the tool's definition Tool name 'list_saved_searches' and description 'List or retrieve saved searches from Splunk' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List or retrieve saved searches from Splunk. It is categorised as a Read tool in the Splunk MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Splunk MCP Server 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 MCP Server. 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 MCP server (rootiq-ai/splunk-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 →