REPORECALL TOOLS

30 tools from the Reporecall MCP Server, categorised by risk level.

READ 23 tools
Read build_stack_tree Build a bidirectional call tree from a seed function/method. Shows callers (who invokes it) and callees (wh... Read business_context_query Find product areas and business capability pages relevant to a query. Returns business-facing context plus ... Read explain_flow Explain the call flow around a query or function name. Resolves a seed symbol, builds a bidirectional call ... Read explain_memory Explain how memory recall would behave for a query, including selected memories, dropped memories, route, a... Read find_callees Find functions called by a given function Read find_callers Find functions that call a given function Read get_communities Get detected code communities (clusters of tightly-coupled modules). Returns community IDs, member counts, ... Read get_hub_nodes Get the most connected nodes (god nodes / architectural hubs) in the call graph. These are functions or cla... Read get_imports Get import statements for a file. Shows what modules/symbols a file imports. Read get_lens_data Return current Reporecall Lens JSON from the existing index. Read-only; call refresh_context first when fre... Read get_stats Get index statistics, conventions, and latency info Read get_surprises Get surprising cross-module connections in the codebase — edges that bridge structurally distant communitie... Read get_symbol Look up code symbols (functions, classes, methods) by name. Returns matching chunks with file path, lines, ... Read list_memories List all stored memories with metadata. Optionally filter by type. Read list_product_areas List product-area aggregates inferred from business wiki pages. Use this for business-facing navigation bef... Read recall_memories Search project and user memories using local keyword retrieval. Returns relevant memories from prior sessions. Read refresh_context Refresh Reporecall context for external tools: re-index code, regenerate deterministic wiki/business pages ... Read search_code Search the codebase using hybrid vector + keyword search Read suggest_investigations Get suggested investigation questions based on codebase topology — weak resolution edges, bridge nodes, hub... Read wiki_check_staleness Check if wiki pages are stale (referenced files changed since page was written). Optionally check a specifi... Read wiki_query Search wiki pages by keyword. Returns matching wiki pages with summaries. Use this to find existing codebas... Read wiki_read Read a wiki page by name, or list all wiki pages if no name is given. Read resolve_seed Resolve a query to seed candidates for stack tree building. Returns ranked code symbols that best match the...

Route Reporecall through PolicyLayer and every one of its 30 tools is checked against your policy before it runs.

GOVERN REPORECALL →

Enforced before the call runs. Nothing to install.

How many tools does the Reporecall MCP server have? +

The Reporecall MCP server exposes 30 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Reporecall tools? +

Route the Reporecall 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 Reporecall tools fall into? +

Reporecall tools are categorised as Read (23), Write (3), Destructive (3), Execute (1). Each category has a recommended default policy.

Enforce policy on every Reporecall tool call.

Deterministic rules across all 30 Reporecall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

42,500+ MCP servers and 110,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.