// MCP TOOL REFERENCE

CONTEXT ENGINE MCP SERVER TOOLS

50 tools from the Context Engine MCP Server MCP Server, categorised by risk level.

View the Context Engine MCP Server policy →

// ALL 50 CONTEXT ENGINE MCP SERVER TOOLS

READ 28 tools

Read call_relationships Return deterministic local callers and/or callees of a known function or method symbol. Use this tool when... Read codebase_retrieval IMPORTANT: This is the PRIMARY tool for searching the codebase. Please consider as the FIRST CHOICE for any... Read find_callees Return deterministic callees of a known function or method symbol. This tool prefers persisted graph call ... Read find_callers Return deterministic callers of a known function or method symbol. This tool prefers persisted graph call ... Read get_context_for_prompt Get relevant codebase context optimized for prompt enhancement. This is the primary tool for understanding ... Read get_file Retrieve complete or partial contents of a file from the codebase. Use this tool when you need to: - View ... Read get_review_status Get the current status and progress of a reactive review session. Returns: - Session status (active, pause... Read get_review_telemetry Get detailed telemetry data for a review session. Returns: - Token usage statistics - Cache hit/miss rates... Read impact_analysis Estimate the direct change surface of a known symbol using graph-backed definition, reference, and call-edg... Read index_status Retrieve current index health metadata (status, last indexed time, file count, staleness). Read list_memories List all stored memories, optionally filtered by category. Shows file stats, entry counts, and content pre... Read list_plans List all saved plans with optional filtering. Read load_plan Load a previously saved plan by ID or name. Read review_auto Smart wrapper that chooses review_diff when a diff is provided; otherwise chooses review_git_diff for the c... Read review_diff Enterprise-grade diff-first review with deterministic preflight and structured JSON output. Read review_memory_suggestions Review draft memory batches and perform idempotent batch actions. Batch listing enforces the Phase 1 cap (... Read semantic_search Perform semantic search across the codebase to find relevant code snippets. Use this tool when you need to... Read symbol_definition Return the single best deterministic declaration site for a known identifier. Use this tool when you need ... Read symbol_references Find non-declaration usages of a known identifier across the local codebase. Use this tool when you need t... Read symbol_search Perform deterministic symbol-first search across the codebase for identifier-style navigation. Use this to... Read tool_manifest Discover available tools and capabilities exposed by the server. Read trace_symbol Trace a known symbol across its canonical definition, non-declaration references, and direct call edges. T... Read view_history View version history for a plan. Read view_progress View execution progress for a plan. Read why_this_context Explain why files were selected into a context bundle using the shared retrieval provenance and explainabil... Read compare_plan_versions Generate a diff between two versions of a plan. Read review_changes Review code changes from a diff using AI-powered analysis. This tool performs a structured code review on ... Read visualize_plan Generate diagrams from an implementation plan. Use this to visualize the plan

WRITE 9 tools

Write start_step Mark a step as in-progress to begin execution. Write fail_step Mark a step as failed with error details. Write add_memory Store a memory for future sessions. Memories are persisted as markdown files and automatically retrieved vi... Write complete_step Mark a step as completed with optional notes. Write create_plan Generate a detailed implementation plan for a software development task. This tool enters Planning Mode, w... Write refine_plan Refine an existing implementation plan based on feedback or clarifications. Use this tool to iterate on a ... Write request_approval Create an approval request for a plan or specific steps. Write rollback_plan Rollback a plan to a previous version. Write save_plan Save a plan to persistent storage for later retrieval and execution tracking.

DESTRUCTIVE 3 tools

Destructive clear_index Remove saved index state and clear caches without rebuilding. Destructive delete_plan Delete a saved plan from storage. Destructive reindex_workspace Clear current index state and rebuild it from scratch.

EXECUTE 10 tools

Execute execute_plan Execute steps from an implementation plan, generating code changes. This tool orchestrates the execution o... Execute index_workspace Index the current workspace for semantic search. This tool scans all source files in the workspace and bui... Execute reactive_review_pr Start a reactive PR code review session. This tool initiates an AI-powered code review with advanced featu... Execute run_static_analysis Run local static analyzers (tsc and optional semgrep) and return structured findings. Execute check_invariants Run YAML invariants deterministically against a unified diff (no LLM). Execute pause_review Pause a running reactive review session. The review can be resumed later with resume_review. Useful for: -... Execute respond_approval Respond to a pending approval request (approve, reject, or request modifications). Execute scrub_secrets Scrub secrets from content before sending to LLM. Detects and masks 15+ types of secrets: - AWS keys, Open... Execute validate_content Run multi-tier validation on content. **Tier 1 (Deterministic):** - Balanced brackets/braces - Valid JSON ... Execute resume_review Resume a paused reactive review session. Continues execution from where it was paused.

// FAQ

How many tools does the Context Engine MCP Server MCP server have? +

The Context Engine MCP Server MCP server exposes 50 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Context Engine MCP Server tools? +

Route the Context Engine MCP Server 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 Context Engine MCP Server tools fall into? +

Context Engine MCP Server tools are categorised as Read (28), Write (9), Destructive (3), Execute (10). Each category has a recommended default policy.

Enforce policy on every Context Engine MCP Server tool call.

Start from Context Engine MCP Server, 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.