git_stash_manager · Claude MCP Server Integration MCP

WHAT IT DOES

What git_stash_manager does on Claude MCP Server Integration

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

WHY IT NEEDS A POLICY

Why git_stash_manager needs a policy

Git stash operations save and restore working directory changes. Stashing writes changes to the stash stack; popping/applying restores them. These are reversible operations (stash can be re-applied or dropped) and do not permanently delete code, making Write the most appropriate category. However, stash drop/clear operations could be destructive if included — the vague description lowers confidence slightly.

From the tool's definition Manage git stash (save/restore changes)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_stash_manager Rate-limited

git_stash_manager 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_stash_manager": {
      "limits": [
        {
          "counter": "git_stash_manager_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 Claude MCP Server Integration, so you can run agents against it safely.

FAQ

Questions about git_stash_manager

What does the git_stash_manager tool do? +

Manage git stash (save/restore changes). It is categorised as a Write tool in the Claude MCP Server Integration 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_stash_manager? +

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

What risk level is git_stash_manager? +

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

Can I rate-limit git_stash_manager? +

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

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

git_stash_manager is provided by the Claude MCP Server Integration MCP server (mokemoke0821/claude-mcp-integration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.