git_status

THE RISK

Low Risk

Why git_status needs a policy

git_status is a read-only git command that reports the current state of tracked/untracked files and staging area. It has no side effects and does not create, modify, or delete data. It is purely informational, making it a Read category tool with low severity.

From the tool's definition Tool name 'git_status' and description 'Get git repository status' indicate a query operation that retrieves information about the git repository state without modifying any files, commits, or repository structure.

Documented attack patterns abuse exactly the kind of access git_status gives an agent:

POLICY

How to control git_status

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP File Edit, and nothing reaches the server without passing your rules. This is the rule we recommend for git_status:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "git_status": {}
  }
}

git_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MCP File Edit — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP File Edit tools

Destructive delete_file Delete a file or directory. Execute git_branch git_branch Execute git_clone Clone a remote git repository. Execute git_init Initialize a new git repository. Execute git_remote git_remote Execute ssh_sync ssh_sync Execute git_checkout Checkout a branch or commit. Execute git_push git_push

All 32 MCP File Edit tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about git_status

What does the git_status tool do? +

Get git repository status. It is categorised as a Read tool in the MCP File Edit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_status? +

Register the MCP File Edit 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 MCP File Edit. Nothing to install.

What risk level is git_status? +

git_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit git_status? +

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.

How do I block git_status completely? +

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.

What MCP server provides git_status? +

git_status is provided by the MCP File Edit MCP server (patrickomatik/mcp-file-edit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP File Edit tool call.

Start from MCP File Edit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →