status
Returns the working tree status as structured data (branch, staged, modified, untracked, conflicts).
This record as markdown: /tools/io-github-dave-london-cargo/status.md
What status does on Cargo
AI agents call status to retrieve information from Cargo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why status is rated Low
The status tool only queries and retrieves information about the current state of the working directory (branch, staged files, modified files, untracked files, and conflicts). It performs no modifications, deletions, code execution, or side effects. This is a classic read operation with minimal security risk.
From the tool's definition Tool description states it "Returns the working tree status as structured data" - a read-only query operation that retrieves git status information without modifying any files or state.
Attacks that exploit this kind of access
The rule that runs status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cargo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For status, this is the rule to start with:
status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cargo, apply this rule, and every status call is checked against it from then on.
Questions about status
Returns the working tree status as structured data (branch, staged, modified, untracked, conflicts). It is categorised as a Read tool in the Cargo MCP Server, which means it retrieves data without modifying state.
Register the Cargo 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 Cargo. Nothing to install.
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 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 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.
status is provided by the Cargo MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cargo, and thousands of servers like it.
This server
Across the catalogue