codegraph_build · VibeServe MCP: Risk & Policy

WHAT IT DOES

What codegraph_build does on VibeServe

AI agents invoke codegraph_build to trigger actions in VibeServe. 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 codegraph_build needs a policy

This tool actively processes and builds structured data artifacts (call graphs, import resolution, class hierarchies, communities) from a repository. It is not a simple read/query — it executes a multi-step analysis pipeline that creates new derived data structures. It does not delete or overwrite source data, nor does it involve financial operations, placing it squarely in Execute.

From the tool's definition 'Build a knowledge graph from an indexed repo — creates call graph, import resolution, class hierarchy, and communities'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

codegraph_build Rate-limited

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

FAQ

Questions about codegraph_build

What does the codegraph_build tool do? +

Build a knowledge graph from an indexed repo — creates call graph, import resolution, class hierarchy, and communities. Prerequisite before using other codegraph_* tools. It is categorised as a Execute tool in the VibeServe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on codegraph_build? +

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

What risk level is codegraph_build? +

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

Can I rate-limit codegraph_build? +

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

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

codegraph_build is provided by the VibeServe MCP server (ncsound919/vibeserve). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.