status

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

SERVERTest 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-test/status.md

WHAT IT DOES

What status does on Test

AI agents call status to retrieve information from Test 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 tool retrieves git repository state information without creating, modifying, or deleting any data. It is purely informational—querying metadata about the working tree. This is a classic Read operation with minimal security risk unless the output itself contains sensitive information, which is unlikely for git status metadata.

From the tool's definition Tool description states it 'Returns the working tree status as structured data (branch, staged, modified, untracked, conflicts).' The verb 'Returns' and the read-only nature of querying git status indicates no modifications or side effects.

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 Test, 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 Test, 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 Test MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on status? +

Register the Test 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 Test. 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 Test 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 Test, and thousands of servers like it.

This server

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