Git status, log, diff dekhna
AI agents call git_status to retrieve information from Universal Dev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
git_status queries git metadata and displays information. The operations mentioned (status, log, diff) are purely informational with no side effects. They do not create, modify, delete, or execute any code. This is a classic Read operation with minimal risk.
From the tool's definition Tool description explicitly states 'Git status, log, diff dekhna' — all read-only operations that retrieve and display git repository state, commit history, and file changes without modifying anything.
Attacks that exploit this kind of access
Git status, log, diff dekhna. It is categorised as a Read tool in the Universal Dev MCP MCP Server, which means it retrieves data without modifying state.
Register the Universal Dev MCP server in PolicyLayer and add a rule for git_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 Universal Dev MCP. Nothing to install.
git_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_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_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_status is provided by the Universal Dev MCP server (kallusuvaidyam/universal_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 →