List all Splunk users (requires admin privileges)
AI agents call list_users 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 user information from Splunk without modifying, executing, or deleting anything. It is a read-only operation. Severity is medium rather than low because it exposes user account information that could be sensitive (usernames, potentially associated metadata), and requires admin privileges, meaning misuse could reveal organizational structure or user details to unauthorized parties.
From the tool's definition Tool name is 'list_users' and description states 'List all Splunk users', which is a retrieval operation with no modification or side effects. The description notes 'requires admin privileges', indicating privileged read access.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access list_users 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_users:
{
"version": "1",
"default": "deny",
"tools": {
"list_users": {}
}
}list_users 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 Splunk users (requires admin privileges). 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_users: 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_users 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_users 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_users. 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_users 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.