AI agents call git_status to retrieve information from PSKit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
git_status retrieves information about the current state of a git repository (staged files, modified files, branch, etc.) with no side effects. It is purely informational, analogous to running 'git status' for inspection only. This is a safe Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'git_status' and description states 'Get the current git status' – a read-only query operation that retrieves git state without modifying data or executing external commands with variable effects.
Attacks that exploit this kind of access
Get the current git status. It is categorised as a Read tool in the PSKit MCP Server, which means it retrieves data without modifying state.
Register the PSKit 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 PSKit. 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 PSKit MCP server (nickalus12/pskit). 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 →