Get basic Splunk connection information and list available apps (same as health_check but for endpoint consistency)
AI agents call health 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 retrieves status and metadata information about Splunk connection state and available applications. It queries existing data without side effects, making it a Read category tool with low severity since it only exposes informational data about the Splunk environment.
From the tool's definition Tool description states: 'Get basic Splunk connection information and list available apps'. The action is retrieval-only with no modification, deletion, or execution of commands. Verb 'Get' and 'list' indicate read-only operations.
Documented attack patterns abuse exactly the kind of access health 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 health:
{
"version": "1",
"default": "deny",
"tools": {
"health": {}
}
}health 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.
Get basic Splunk connection information and list available apps (same as health_check but for endpoint consistency). 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 health: 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.
health 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 health 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 health. 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.
health 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.