status

THE RISK

Low Risk

Why status needs a policy

The 'status' tool retrieves information about repository state (modified files, staging area, branch info, etc.). This is a read-only operation with no side effects, consistent with Git's 'git status' command. No data is created, modified, deleted, or executed. Severity is low because misuse of a status query cannot cause harm—it only reveals information already available to the user.

From the tool's definition Tool name 'status' and description 'Get repository status' indicate a retrieval-only operation that queries the current state of a Git repository without modifying, executing, or deleting anything.

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

POLICY

How to control status

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

policy.json

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

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 Git MCP Server — 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 Git MCP Server tools

Destructive branch_delete Delete a branch Destructive remote_remove Remove a remote Destructive stash_pop Apply and remove a stash Destructive tag_delete Delete a tag Execute bulk_action Execute multiple Git operations in sequence. This is the preferred way to execute multiple Execute checkout Switch branches or restore working tree files Write add Stage files Write branch_create Create a new branch

All 21 Git MCP Server 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 status

What does the status tool do? +

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

How do I enforce a policy on status? +

Register the Git MCP Server MCP server in PolicyLayer and add a rule for 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 MCP Server. Nothing to install.

What risk level is status? +

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

Can I rate-limit status? +

Yes. Add a rate_limit block to the 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 status completely? +

Set action: deny in the PolicyLayer policy for 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 status? +

status is provided by the Git MCP Server MCP server (sheshiyer/git-mcp-v2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Git MCP Server tool call.

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

CHECK YOUR STACK →