git_status

Show the current git status of the workspace (changed files, staged files, branch info). Use this to understand what files have been modified before committing.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/git-status.md

WHAT IT DOES

What git_status does on CoWork OS

AI agents call git_status to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why git_status is rated Low

git_status performs read-only queries of git repository metadata (changed files, staged files, branch info). It has no side effects, does not execute arbitrary code, does not modify data, and does not delete anything. This is a straightforward read operation with minimal risk even if misused by an AI agent, as it only reveals local filesystem state already known to the system.

From the tool's definition Tool description explicitly states 'Show the current git status' and 'Use this to understand what files have been modified' — purely informational operations that retrieve and display repository state without modifying anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_status, this is the rule to start with:

git_status Allowed

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

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every git_status call is checked against it from then on.

FAQ

Questions about git_status

What does the git_status tool do? +

Show the current git status of the workspace (changed files, staged files, branch info). Use this to understand what files have been modified before committing. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on git_status? +

Register the CoWork OS 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 CoWork OS. 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 CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →