code_repo_set · Yaver MCP: Risk & Policy

WHAT IT DOES

What code_repo_set does on Yaver

AI agents use code_repo_set 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	Description
`query`	string	Yes	Repo/project selector or absolute path
`device_id`	string	—	Optional remote device ID

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why code_repo_set needs a policy

An AI agent can call code_repo_set 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.

Risk signalsAccepts freeform code/query input (query)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

code_repo_set Rate-limited

code_repo_set 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": {
    "code_repo_set": {
      "limits": [
        {
          "counter": "code_repo_set_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 code_repo_set

What does the code_repo_set tool do? +

Switch the active repo/workdir for yaver code on the local or attached target. Accepts a project name, slug, or absolute path. Optional device_id updates another owned Yaver machine. 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 code_repo_set accept? +

code_repo_set accepts 2 parameters: query, device_id. Required: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on code_repo_set? +

Register the Yaver MCP server in PolicyLayer and add a rule for code_repo_set: 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 code_repo_set? +

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

Can I rate-limit code_repo_set? +

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

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

code_repo_set 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.