LOCAL RAG TOOLS

29 tools from the Local Rag MCP Server, categorised by risk level.

READ 23 tools
Read affected Given changed files (or the working-tree diff against HEAD by default), report the test files that transiti... Read git_context Show git context for the working tree: uncommitted changes annotated with index status, recent commits, and... Read impact Symbol-level blast radius: the transitive callers of a function or method as a pruned call tree, plus the t... Read callees List the functions/methods a symbol directly calls (one hop out), each resolved to its definition file:line... Read dependents List all files that import a given file (reverse dependencies). Shows the blast radius before modifying a f... Read depends_on List all files that a given file imports (its dependencies). Shows the resolved import graph — what this fi... Read file_history Get the commit history for a specific file. Returns commits that touched the file, sorted by date (newest f... Read get_annotations Retrieve persistent notes attached to files or symbols. Pass path to get all notes for a file. Pass query t... Read index_status Show the current state of the RAG index for a project directory. Read list_checkpoints List conversation checkpoints, most recent first. Cross-session by default. Read project_map Visualize how files relate to each other — imports, exports, and fan-in/fan-out. Faster than reading import... Read read_conversation Read the full verbatim text of past conversation turns by session + turn index. The read counterpart to sea... Read read_relevant Get the actual content of the most relevant code chunks — individual functions, classes, or sections — with... Read search Search the full codebase by meaning — finds files that grep misses. Use natural language ( Read search_analytics Show search usage analytics: query counts, zero-result queries, low-relevance queries, top searched terms. Read search_checkpoints Semantic search over checkpoint titles and summaries. Read search_commits Semantically search git commit history. Use this to find why code was changed, when decisions were made, or... Read search_conversation Search through conversation history. Finds past decisions, discussions, and tool outputs from current or pr... Read search_symbols Find where a function, class, type, or interface is defined — by name, not semantics. Faster than grep for ... Read server_info Show the current MCP server configuration: resolved project directory, database location, index status, emb... Read trace Show how one symbol reaches another: the connecting call sub-graph from Read usages Find call sites and references to a symbol across indexed files — with file paths, line numbers, and matchi... Read write_relevant Find the best file and location to insert new code or docs. Returns semantically appropriate insertion poin...

Route Local Rag through PolicyLayer and every one of its 29 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

How many tools does the Local Rag MCP server have? +

The Local Rag MCP server exposes 29 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Local Rag tools? +

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

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

Enforce policy on every Local Rag tool call.

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

Free to start. No card required.

43,000+ MCP servers and 220,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.