// MCP TOOL REFERENCE

GRAPHHUB TOOLS

32 tools from the GraphHub MCP Server, categorised by risk level.

// ALL 32 GRAPHHUB TOOLS

READ 26 tools

Read batch_context Get definition + caller/callee counts for multiple symbols in one call. Replaces N get_context calls when a... Read changed_symbols List the symbols in files changed by the current branch (or working tree / staged diff). Each entry include... Read check_arch_rules Enforce architecture boundary rules — detect files that import across forbidden layer boundaries. Rules can... Read explain_search Explain how a search query will be processed. Shows tokenization and search strategy. Read find_cycles Detect circular import chains or mutual-recursion call cycles in the codebase. Returns each cycle as an ord... Read find_dead_code Find functions, methods, and classes that are never called by anything in the graph. Useful before refactor... Read find_duplicates Find functions that are semantically similar to a given symbol — likely duplicate or near-duplicate impleme... Read find_similar Find symbols that are semantically similar to a given symbol. Useful for finding related code. Read find_tech_debt Surface TODO/FIXME/HACK/OPTIMIZE markers stored in the graph during indexing. Returns symbols sorted by ris... Read get_context Get all callers and callees of a symbol by name. Shows the full call graph context around a function or class. Read get_file_symbols Retrieve all symbols (classes, functions, etc.) defined in a specific file. Read get_hierarchy Explore the inheritance and interface implementation tree for a class or interface. Returns ancestors (pare... Read get_observation Get a specific observation by its ID. Read get_test_coverage Show which functions and methods in the codebase are exercised by test files. Identifies uncovered symbols ... Read impact_analysis Analyze all symbols that directly call or import a given symbol. Shows what would break if the symbol changes. Read memory_stats Get statistics about stored observations: totals, counts by type, by project, by importance. Read recall Search memory for past observations using natural language. Returns results ranked by semantic similarity. Read recall_bugfix Find past bug fixes with similar symptoms. Returns structured fix patterns (symptom/root_cause/fix) ranked ... Read recall_skill_choice Find which skill was used for similar past tasks. Skip the skill-selection decision for common task patterns. Read related_observations Get all observations that are linked to a specific code symbol. Read review_diff Generate a structured pre-merge review of the current git diff. Returns each changed symbol with its blast ... Read search_by_name Search for symbols by their name. Supports exact or fuzzy matching. Read search_grouped Search for code and group results by file. Useful for understanding which files are most relevant. Read semantic_search Search for code using natural language. Supports semantic (meaning-based), keyword, or hybrid search modes. Read timeline View observations chronologically. Useful for reviewing what happened during a session or project. Read debug_trace One-shot debugging entry point. Given a bug description or error message, returns ranked candidate symbols ...

WRITE 4 tools

Write remember_bugfix Record a resolved bug so future agents can reuse the fix pattern. Stores symptom, root cause, and fix as a ... Write remember_skill_choice Cache which .skill.md / SKILL.md file was used for a task so similar future tasks route to the same skill w... Write remember Save a learning, decision, finding, or other observation to persistent memory. Searchable via recall with s... Write update_observation Update an existing observation

DESTRUCTIVE 1 tools

Destructive forget Delete observations from memory. Can delete by ID, session, project, type, or date.

EXECUTE 1 tools

Execute query_graph Run a direct Cypher query against the codebase graph database. Use this to find complex relationships.

// FAQ

How many tools does the GraphHub MCP server have? +

The GraphHub MCP server exposes 32 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on GraphHub tools? +

Route the GraphHub server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do GraphHub tools fall into? +

GraphHub tools are categorised as Read (26), Write (4), Destructive (1), Execute (1). Each category has a recommended default policy.

Enforce policy on every GraphHub tool call.

Start from GraphHub, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.