AI agents call fabric_cve_stats to retrieve information from Git Steer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays aggregate statistics and status information about CVE vulnerabilities. It performs read-only operations on a monitoring/reporting dashboard without creating, modifying, deleting data, or triggering external operations.
From the tool's definition Tool name and description indicate a dashboard that displays CVE queue metrics: 'totals by status/severity, oldest pending, top repos' — these are informational queries with no modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
[git-fabric] CVE queue health dashboard: totals by status/severity, oldest pending, top repos. It is categorised as a Read tool in the Git Steer MCP Server, which means it retrieves data without modifying state.
Register the Git Steer MCP server in PolicyLayer and add a rule for fabric_cve_stats: 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 Git Steer. Nothing to install.
fabric_cve_stats 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 fabric_cve_stats 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 fabric_cve_stats. 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.
fabric_cve_stats is provided by the Git Steer MCP server (ry-ops/git-steer). 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 →