Get Splunk server information and health status.
AI agents call get_server_info 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 retrieves server metadata and health metrics without creating, modifying, deleting, or executing any operations. It is a passive information-gathering operation typical of Read category tools. Severity is low because server info disclosure has minimal blast radius—it reveals system status but does not enable data manipulation or command execution.
From the tool's definition Tool name 'get_server_info' and description 'Get Splunk server information and health status' indicate a query/retrieval operation with no modification or execution capabilities.
Attacks that exploit this kind of access
Get Splunk server information and health status. 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 get_server_info: 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.
get_server_info 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 get_server_info 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 get_server_info. 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.
get_server_info 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 →