fleet_git_status

THE RISK

Low Risk

Why fleet_git_status needs a policy

This tool performs a query operation that returns the current Git state without side effects. It gathers metadata about repository branches, working directory cleanliness, and onboarding status—all read-only operations. No data is created, modified, deleted, or executed.

From the tool's definition fleet_git_status retrieves Git state information (branch, clean/dirty, onboard status) for one or all apps without modifying any data or triggering operations.

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

POLICY

How to control fleet_git_status

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

policy.json

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

fleet_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 Fleet — 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 Fleet tools

Execute fleet_audit_run Run an App Store compliance audit on a mobile app project via greenlight preflight. Execute fleet_deploy Deploy an app: build and restart Execute fleet_secrets_unseal Decrypt vault to /run/fleet-secrets/. WARNING: This overwrites any runtime changes that we Execute fleet_deps_scan Run a fresh dependency scan across all registered apps Execute fleet_git_push Push current branch to origin Write fleet_deps_fix Create a PR with dependency updates for an app (dry-run by default) Write fleet_audit_ignore Suppress a confirmed greenlight false positive from future audits. The finding is Write fleet_secrets_seal Seal runtime secrets back to the encrypted vault.

All 39 Fleet 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 fleet_git_status

What does the fleet_git_status tool do? +

Git state for one or all apps: branch, clean/dirty, onboard status. It is categorised as a Read tool in the Fleet MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fleet_git_status? +

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

What risk level is fleet_git_status? +

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

Can I rate-limit fleet_git_status? +

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

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

fleet_git_status is provided by the Fleet MCP server (wrxck/fleet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fleet tool call.

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

CHECK YOUR STACK →