8 tools from the GraphPulse C++ MCP Server, categorised by risk level.
View the GraphPulse C++ policy →analyze_codebase
Ingest a C++ codebase and build its dependency graph.
This tool does NOT accept 'code_content'. Provide exactly ONE of:
repo_url, raw_... detect_cycles
Detect circular dependencies in the current call graph.
Returns:
Formatted list of cycles, or a message if none found.
get_callees
List downstream functions that are called by the given function.
Args:
function_name: Exact name of the function (e.g., 'process_... get_callers
List upstream functions that call the given function.
Args:
function_name: Exact name of the function (e.g., 'calculate_interest'... get_file_coupling
Generate a report showing which files depend on which other files.
Aggregates cross-file function calls into a per-file-pair summary
... get_file_functions
List all functions defined in a specific source file.
Use the relative path exactly as returned in the analyze_codebase
output (e.g.,... get_orphan_functions
Identify functions that are defined but never called by any other function.
Returns:
Comma-separated list of orphan function name... The GraphPulse C++ MCP server exposes 8 tools across 2 categories: Read, Write.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the GraphPulse C++ server.
GraphPulse C++ tools are categorised as Read (7), Write (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept