Get the current repository status
AI agents call get_repo_status to retrieve information from Git Memory 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 repository metadata (branch, uncommitted changes, file status, etc.) with no side effects. It is analogous to running 'git status', which is a read-only query operation. No data is created, modified, deleted, or executed. The low severity reflects minimal risk even if misused by an agent—exposure of repository state information is non-destructive.
From the tool's definition Tool name 'get_repo_status' and description 'Get the current repository status' indicate a retrieval operation that queries the state of a Git repository without modifying data.
Attacks that exploit this kind of access
Get the current repository status. It is categorised as a Read tool in the Git Memory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Git Memory MCP Server MCP server in PolicyLayer and add a rule for get_repo_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 Git Memory MCP Server. Nothing to install.
get_repo_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 get_repo_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 get_repo_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.
get_repo_status is provided by the Git Memory MCP Server MCP server (nirutyodjai/git-memory-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 →