status

Returns the working tree status as structured data (branch, staged, modified, untracked, conflicts).

SERVERSearch SOURCEDave-London/Pare

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/io-github-dave-london-pare-search/status.md

WHAT IT DOES

What status does on Search

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

RISK

Why status is rated Low

The 'status' tool is a read-only operation that retrieves git repository metadata. It queries the current state of the working directory without making any changes. This is a standard diagnostic/inspection operation with minimal blast radius if misused by an AI agent—it cannot cause data loss, execute arbitrary code, or modify files. Low severity and high confidence are appropriate.

From the tool's definition Tool returns 'working tree status as structured data (branch, staged, modified, untracked, conflicts)' - purely informational queries with no modification, creation, deletion, or execution of code or commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Search, 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 Allowed

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": {
    "status": {}
  }
}

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

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

FAQ

Questions about status

What does the status tool do? +

Returns the working tree status as structured data (branch, staged, modified, untracked, conflicts). It is categorised as a Read tool in the Search MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on status? +

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

KEEP EXPLORING

More on Search, and thousands of servers like it.

This server

All 202 Search 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 →