git_submodule · Git MCP: Risk & Policy

WHAT IT DOES

What git_submodule does on Git

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

WHY IT NEEDS A POLICY

Why git_submodule needs a policy

Submodule operations that add or update create new entries in .gitmodules and modify the repository structure. While these are reversible changes (unlike destructive operations), they alter the repository state and can introduce external code dependencies. The most severe capability is 'add' and 'update', which are write operations.

From the tool's definition Tool description states 'Add, list, update, or sync submodules' — the add, update, and sync operations modify the repository configuration and potentially fetch external code, while list is read-only.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_submodule Rate-limited

git_submodule 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": {
    "git_submodule": {
      "limits": [
        {
          "counter": "git_submodule_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 Git, so you can run agents against it safely.

FAQ

Questions about git_submodule

What does the git_submodule tool do? +

Add, list, update, or sync submodules. It is categorised as a Write tool in the Git MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on git_submodule? +

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

What risk level is git_submodule? +

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

Can I rate-limit git_submodule? +

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

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

git_submodule is provided by the Git MCP server (selfagency/git-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.