nogra_repo_status

Read-only git status snapshot for the local workflow repo.

SERVERNogra SOURCE@nograai/mcp

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-nograai-nogra-mcp/nogra-repo-status.md

WHAT IT DOES

What nogra_repo_status does on Nogra

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

RISK

Why nogra_repo_status is rated Low

This tool retrieves git status information from a local repository without side effects. It is purely informational, making it a Read category tool with low severity since it cannot be misused to cause harm—it only exposes repository state information that an agent would typically already have access to in a local workflow context.

From the tool's definition Tool name includes 'status' (query operation); description explicitly states 'Read-only git status snapshot' with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nogra_repo_status safely

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

nogra_repo_status Allowed

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

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

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

FAQ

Questions about nogra_repo_status

What does the nogra_repo_status tool do? +

Read-only git status snapshot for the local workflow repo. It is categorised as a Read tool in the Nogra MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on nogra_repo_status? +

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

What risk level is nogra_repo_status? +

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

Can I rate-limit nogra_repo_status? +

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

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

nogra_repo_status is provided by the Nogra MCP server (@nograai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nogra, and thousands of servers like it.

This server

All 45 Nogra 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 →