Analyze uncommitted changes in the Git repository to suggest the correct Conventional Commit prefix.
AI agents call git_current_work_status to retrieve information from ContextCore MCP 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 the current state of uncommitted Git changes to provide suggestions. It performs no writes, deletions, or code execution—only inspection and analysis of local repository state. The blast radius of misuse is minimal (an incorrect suggestion for a commit prefix, which the user controls).
From the tool's definition Tool name 'git_current_work_status' and description 'Analyze uncommitted changes in the Git repository to suggest the correct Conventional Commit prefix' indicate the tool queries/reads Git state without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Analyze uncommitted changes in the Git repository to suggest the correct Conventional Commit prefix. It is categorised as a Read tool in the ContextCore MCP MCP Server, which means it retrieves data without modifying state.
Register the ContextCore MCP server in PolicyLayer and add a rule for git_current_work_status: 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 ContextCore MCP. Nothing to install.
git_current_work_status 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 git_current_work_status 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 git_current_work_status. 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.
git_current_work_status is provided by the ContextCore MCP server (rkpraveendev/contextcore-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 →