// MCP TOOL REFERENCE

ENGRAMS TOOLS

42 tools from the Engrams MCP Server, categorised by risk level.

// ALL 42 ENGRAMS TOOLS

READ 24 tools

Read check_compliance Evaluates a specific existing item (by item_type and item_id) against all applicable governance rules. Use ... Read get_active_context Retrieves the session-level active context: current work focus, open issues, and recent changes. This is the Read get_bindings_for_item Lists all code bindings attached to a specific Engrams entity (by item_type and item_id). Use to see which ... Read get_context_for_files Given file paths being edited, returns ALL Engrams entities (decisions, patterns, etc.) bound to those path... Read get_custom_data Retrieves custom data entries by exact category and/or key lookup. Provide category alone to list all entri... Read get_decisions Lists decisions, filtered by tags or ordered by recency. Use when you want to browse/filter decisions by ta... Read get_effective_context Retrieves the merged governance view for a specific individual scope: team-level items (taking precedence) ... Read get_governance_rules Lists the active governance rules for a specific scope, optionally filtered by entity_type (e.g., Read get_item_history Retrieves version history for Product Context or Active Context ONLY (not decisions, progress, or other ent... Read get_linked_items Retrieves all knowledge graph links for a specific item (both outgoing and incoming). Use to explore relati... Read get_product_context Retrieves the stored high-level product context (project goals, features, architecture) as a single JSON ob... Read get_progress Lists progress/task entries, optionally filtered by status (e.g., Read get_project_briefing Generates a structured, human-readable project briefing at a specified depth level. Levels: Read get_recent_activity_summary Returns a digest of recently created or updated items across all entity types, ideal for session start catc... Read get_relevant_context Returns the OPTIMAL subset of ALL Engrams entities (decisions, patterns, progress, custom data) that fit wi... Read get_scope_amendments Lists proposed changes (amendments) to governance scopes, optionally filtered by status ( Read get_scopes Lists all governance scopes in the workspace, optionally filtered by scope_type ( Read get_system_patterns Lists system/coding patterns, optionally filtered by tags. Returns most recent first. Use to review establi... Read search_custom_data_value_fts Keyword search across ALL custom data entries (values, categories, and keys) using SQLite FTS. Optionally n... Read search_decisions_fts Keyword search across decision text (summary, rationale, implementation_details, tags) using SQLite FTS. Us... Read semantic_search_engrams Natural-language conceptual search across ALL Engrams entity types (decisions, patterns, progress, custom d... Read suggest_bindings Analyzes an Engrams entity Read tool_check_planned_action Pre-mutation governance check: verifies a planned action against all accepted team decisions before any wor... Read verify_bindings Validates code bindings against the actual filesystem — checks which file_pattern globs still match real fi...

WRITE 16 tools

Write batch_log_items Logs multiple items of the SAME type in a single call, reducing round-trips. Supported item_types: Write bind_code_to_item Creates a code binding linking an Engrams entity to file paths via glob patterns. Valid item_type values: Write link_engrams_items Creates a directional relationship link between two Engrams items (e.g., a decision Write log_custom_data Stores or updates a custom key-value entry organized by category. Use for any structured data not covered b... Write log_governance_rule Creates an enforcement rule within a governance scope. Rules define what is blocked or warned for specific ... Write log_system_pattern Creates or updates a named system/coding pattern (e.g., Write review_amendment Accepts or rejects a proposed governance scope amendment. Precondition: the amendment must exist and be in ... Write create_scope Creates a new governance scope (container for rules and items). Two types: Write export_engrams_to_markdown Exports ALL Engrams data (decisions, patterns, progress, custom data, contexts, links) to a directory of ma... Write import_markdown_to_engrams Imports Engrams data from a directory of markdown files previously created by export_engrams_to_markdown. R... Write log_decision Creates a new STRATEGIC decision record — architectural choices, technology selections, coding conventions,... Write log_progress Creates a new progress/task entry with a status (TODO, IN_PROGRESS, DONE, etc.). Use this when a task begin... Write manage_budget_config Reads or updates scoring weight configuration for get_relevant_context. Omit weights to read current config... Write update_active_context Overwrites or patches the session-level active context (current focus, open issues, recent changes). Provid... Write update_product_context Overwrites or patches the persistent product context (project goals, features, architecture). Provide conte... Write update_progress Modifies an existing progress entry by its ID. Use to change status (e.g., IN_PROGRESS → DONE), update desc...

DESTRUCTIVE 2 tools

Destructive delete_item Permanently deletes an Engrams item. For decisions, patterns, and progress entries: provide item_type and i... Destructive unbind_code_from_item Permanently removes a code binding by its numeric binding_id. Destructive and irreversible. Precondition: o...

// FAQ

How many tools does the Engrams MCP server have? +

The Engrams MCP server exposes 42 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Engrams tools? +

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

Engrams tools are categorised as Read (24), Write (16), Destructive (2). Each category has a recommended default policy.

Enforce policy on every Engrams tool call.

Start from Engrams, 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.