skill_publish_to_git · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What skill_publish_to_git does on LocalAnt

AI agents invoke skill_publish_to_git to trigger actions in LocalAnt. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why skill_publish_to_git needs a policy

This tool runs git operations (init and commit) on a local directory, which are executable actions that modify repository state. While committing is technically reversible (commits can be undone), the 'execute' category fits because it triggers external git operations rather than simply creating/modifying data. It does not push remotely on its own, which keeps severity at medium rather than high.

From the tool's definition Initialize/commit a skill directory ready to push to a git remote

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

skill_publish_to_git Rate-limited

skill_publish_to_git stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "skill_publish_to_git": {
      "limits": [
        {
          "counter": "skill_publish_to_git_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about skill_publish_to_git

What does the skill_publish_to_git tool do? +

Initialize/commit a skill directory ready to push to a git remote. It is categorised as a Execute tool in the LocalAnt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on skill_publish_to_git? +

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

What risk level is skill_publish_to_git? +

skill_publish_to_git is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit skill_publish_to_git? +

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

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

skill_publish_to_git is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.