Summarizes development progress and technical debt.
AI agents call work_summary to retrieve information from Git Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval and summarization tool that analyzes existing repository state to generate reports. It has no capability to execute commands, modify code, delete data, or commit financial transactions. The low severity reflects minimal risk: worst case is inaccurate or misleading summary information.
From the tool's definition Tool is described as 'Summarizes development progress and technical debt' without any modification, execution, or deletion capabilities.
Attacks that exploit this kind of access
Summarizes development progress and technical debt. It is categorised as a Read tool in the Git Context MCP Server, which means it retrieves data without modifying state.
Register the Git Context MCP server in PolicyLayer and add a rule for work_summary: 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 Context. Nothing to install.
work_summary 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 work_summary 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 work_summary. 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.
work_summary is provided by the Git Context MCP server (tamishaks-2/git-context-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 →