managed_git_enable · Yaver MCP: Risk & Policy

WHAT IT DOES

What managed_git_enable does on Yaver

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

PARAMETERS

Parameter	Type	Required
`name`	string	—
`slug`	string	—
`work_dir`	string	—
`visibility`	string	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why managed_git_enable needs a policy

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

managed_git_enable Rate-limited

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

FAQ

Questions about managed_git_enable

What does the managed_git_enable tool do? +

Turn on Yaver Managed Git for an existing project. Creates a private managed repo on main by default and records it in project metadata. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does managed_git_enable accept? +

managed_git_enable accepts 4 parameters: name, slug, work_dir, visibility. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on managed_git_enable? +

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

What risk level is managed_git_enable? +

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

Can I rate-limit managed_git_enable? +

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

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

managed_git_enable is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.