[git-fabric] Compact the CVE queue by removing resolved entries older than the retention period.
AI agents call fabric_cve_compact to permanently remove resources in Git Steer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes/deletes CVE queue entries that are considered resolved and past the retention period. 'Removing' records is irreversible data deletion. While scoped to resolved/aged entries, the deletion of audit/security records cannot be undone, making this Destructive. High severity because CVE records are security-critical audit data and their loss could impair compliance and incident response.
From the tool's definition Compact the CVE queue by removing resolved entries older than the retention period
Attacks that exploit this kind of access
[git-fabric] Compact the CVE queue by removing resolved entries older than the retention period. It is categorised as a Destructive tool in the Git Steer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Git Steer MCP server in PolicyLayer and add a rule for fabric_cve_compact: 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_compact is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the fabric_cve_compact 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_compact. 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_compact 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 →