Execute a Splunk search query and return the results. Args: search_query: The search query to execute earliest_time: Start time for the search (default: 24 hours ago) latest_time: End time for the search (default: now) max_results: Maximum number of results to return (default: 100) Returns: List ...
AI agents call search_splunk 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 performs read-only operations on Splunk data. While it executes a search query, the search itself is a data retrieval operation (querying/fetching) rather than a code execution, destructive action, or modification. The parameters allow filtering existing data by time range and result limit, but do not permit creating, modifying, or deleting data.
From the tool's definition Tool description states 'Execute a Splunk search query and return the results' with arguments for query parameters (search_query, earliest_time, latest_time, max_results) and returns 'List of search results'.
Documented attack patterns abuse exactly the kind of access search_splunk 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 search_splunk:
{
"version": "1",
"default": "deny",
"tools": {
"search_splunk": {}
}
}search_splunk 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.
Execute a Splunk search query and return the results. Args: search_query: The search query to execute earliest_time: Start time for the search (default: 24 hours ago) latest_time: End time for the search (default: now) max_results: Maximum number of results to return (default: 100) Returns: List of search results. 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 search_splunk: 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.
search_splunk 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 search_splunk 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 search_splunk. 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.
search_splunk 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.