Track velocity trends over time
AI agents call get_velocity_trends to retrieve information from Git Metrics 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 and analyzes git repository metrics (velocity trends) to provide insights on development patterns. It is a read-only query operation that has no side effects on the repository, code, or any external systems. The blast radius of misuse is minimal—an agent could only request trend analysis that might reveal development insights, with no capability to modify, delete, or execute operations.
From the tool's definition Tool name 'get_velocity_trends' and description 'Track velocity trends over time' indicate data retrieval only. Sibling tools are all get_* methods that query git repository metrics without modification.
Attacks that exploit this kind of access
Track velocity trends over time. It is categorised as a Read tool in the Git Metrics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Git Metrics MCP Server MCP server in PolicyLayer and add a rule for get_velocity_trends: 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 Metrics MCP Server. Nothing to install.
get_velocity_trends 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_velocity_trends 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_velocity_trends. 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_velocity_trends is provided by the Git Metrics MCP Server MCP server (jonmatum/git-metrics-mcp-server). 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 →