Retrieves system metrics from the Cribl deployment. \nIMPORTANT: To avoid excessively large responses, please use the optional parameters (filterExpr, metricNameFilter, earliest, latest, numBuckets, wp) to narrow down your query whenever possible. \nIf no parameters are provided, the server will ...
AI agents call cribl_getSystemMetrics to retrieve information from Cribl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves monitoring/observability data from the Cribl deployment with no side effects. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because unauthorized access to system metrics poses minimal risk compared to tools that modify configurations or execute operations.
From the tool's definition Tool description explicitly states it 'Retrieves system metrics' with optional filtering parameters (filterExpr, metricNameFilter, earliest, latest, numBuckets, wp). No modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
Retrieves system metrics from the Cribl deployment. \nIMPORTANT: To avoid excessively large responses, please use the optional parameters (filterExpr, metricNameFilter, earliest, latest, numBuckets, wp) to narrow down your query whenever possible. \nIf no parameters are provided, the server will default to fetching only the most recent data bucket (numBuckets=1) to prevent performance issues. It is categorised as a Read tool in the Cribl MCP Server, which means it retrieves data without modifying state.
Register the Cribl MCP server in PolicyLayer and add a rule for cribl_getSystemMetrics: 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 Cribl. Nothing to install.
cribl_getSystemMetrics 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 cribl_getSystemMetrics 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 cribl_getSystemMetrics. 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.
cribl_getSystemMetrics is provided by the Cribl MCP server (pebbletek/cribl-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 →