AI agents call codegraph_query to retrieve information from VibeServe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries code metadata (symbols, callers, callees, file locations) and returns information. It performs no modifications, deletions, code execution, or external operations. It is a pure read operation analogous to a grep-style search over a knowledge graph, which is explicitly stated in the description. No write, destructive, execution, or financial risks are present.
From the tool's definition Tool is described as 'Search the knowledge graph for symbols' and 'returns callers, callees, file locations, and export status.' The verb 'search' and 'returns' indicate read-only retrieval of code structure metadata with no side effects.
Attacks that exploit this kind of access
Search the knowledge graph for symbols — returns callers, callees, file locations, and export status. Replaces grep for structural code questions. It is categorised as a Read tool in the VibeServe MCP Server, which means it retrieves data without modifying state.
Register the VibeServe MCP server in PolicyLayer and add a rule for codegraph_query: 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.
codegraph_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the codegraph_query 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.
Set action: deny in the PolicyLayer policy for codegraph_query. 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.
codegraph_query 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →