AI agents call cribl_versionControl 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 retrieves and queries the status of version control settings on the Cribl instance. It does not create, modify, delete, execute code, or move money. The action is purely informational inspection of existing configuration, making it a Read category tool with low severity since exposing git configuration status poses minimal risk to the system.
From the tool's definition Tool description states it 'Detects if version control (git) is enabled' and checks 'whether a remote repository URL is configured' — these are read-only queries of configuration state with no side effects.
Attacks that exploit this kind of access
Detects if version control (git) is enabled on the Cribl instance and whether a remote repository URL is configured. 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_versionControl: 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_versionControl 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_versionControl 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_versionControl. 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_versionControl 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 →