mcp_git_diagnose · Local Code MCP: Risk & Policy

WHAT IT DOES

What mcp_git_diagnose does on Local Code

AI agents use mcp_git_diagnose to create or update resources in Local Code — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local Code environment.

WHY IT NEEDS A POLICY

Why mcp_git_diagnose needs a policy

An AI agent can call mcp_git_diagnose faster than any human can review — one bad instruction and it creates or modifies resources in Local Code by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mcp_git_diagnose Rate-limited

mcp_git_diagnose stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mcp_git_diagnose": {
      "limits": [
        {
          "counter": "mcp_git_diagnose_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Local Code, so you can run agents against it safely.

FAQ

Questions about mcp_git_diagnose

What does the mcp_git_diagnose tool do? +

Diagnose Git execution from inside the MCP server process. It is categorised as a Write tool in the Local Code MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mcp_git_diagnose? +

Register the Local Code MCP server in PolicyLayer and add a rule for mcp_git_diagnose: 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 Local Code. Nothing to install.

What risk level is mcp_git_diagnose? +

mcp_git_diagnose is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mcp_git_diagnose? +

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

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

mcp_git_diagnose is provided by the Local Code MCP server (js190-prog/local-code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.