copilot_complete · Yaver MCP: Risk & Policy

WHAT IT DOES

What copilot_complete does on Yaver

AI agents use copilot_complete 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
`file`	string	—
`model`	string	—	Ollama tag, default qwen2.5-coder:7b
`prefix`	string	Yes	Text before the cursor
`suffix`	string	—	Text after the cursor for FIM
`language`	string	—
`maxTokens`	integer	—
`temperature`	number	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why copilot_complete needs a policy

An AI agent can call copilot_complete 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 file system path (file)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copilot_complete Rate-limited

copilot_complete 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": {
    "copilot_complete": {
      "limits": [
        {
          "counter": "copilot_complete_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 copilot_complete

What does the copilot_complete tool do? +

Generate a code completion via the dev's local Ollama model. Supports fill-in-the-middle via prefix+suffix for Qwen2.5-Coder / StarCoder / DeepSeek. Replaces GitHub Copilot / Cursor for solo devs running Ollama. 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 copilot_complete accept? +

copilot_complete accepts 7 parameters: file, model, prefix, suffix, language, maxTokens, temperature. Required: prefix. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on copilot_complete? +

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

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

Can I rate-limit copilot_complete? +

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

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

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