14 tools from the Lex MCP Server, categorised by risk level.
View the Lex policy →atlas_analyze Analyze code structure and dependencies across modules. Alias: code_atlas (deprecated) contradictions_scan Scan frames for potential contradictions (conflicting information across frames). Returns pairs of frames with detected conflicts and confidence sc... db_stats Get database statistics including frame count, storage size, and activity metrics. Useful for understanding memory usage and recent activity. frame_get Retrieve a specific frame by ID. Use when you know the exact frame ID. Alias: get_frame (deprecated) frame_list List recent Frames, optionally filtered by branch or module. Returns Frame + Atlas Frame for each result. Alias: list_frames (deprecated) frame_search Search Frames by reference point, branch, or Jira ticket. Returns Frame + Atlas Frame neighborhood. Alias: recall (deprecated) frame_validate Validate frame input without storing (dry-run validation). Alias: validate_remember (deprecated) help Get usage help for Lex MCP tools including examples, required fields, related tools, and common workflows. Use this to understand how to use Lex to... hints_get Retrieve hint details by hint ID. Hints are stable, cacheable advice snippets for error recovery. Hint IDs are provided in compact error responses ... policy_check Validate code against policy rules from lexmap.policy.json 2/5 system_introspect Discover the current state of Lex (available modules, policy, frame count, capabilities, error codes with metadata). Returns error code categories ... 2/5 timeline_show Show visual timeline of Frame evolution for a ticket or branch. Alias: timeline (deprecated) turncost_calculate Calculate Turn Cost governance metrics for a time period. Returns frame count, estimated tokens, and prompt count to help measure coordination over... The Lex MCP server exposes 14 tools across 2 categories: Read, Write.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Lex server.
Lex tools are categorised as Read (13), Write (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept