pre_edit_check
RARELY NEEDED — the PreToolUse hook auto-runs this before every edit. Call manually only for an explicit impact check (past mistakes, loop risk, scope violations).
This record as markdown: /tools/20alexl-claude-engram/pre-edit-check.md
What pre_edit_check does on Claude Engram
AI agents call pre_edit_check to retrieve information from Claude Engram without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pre_edit_check is rated Low
The tool performs a pre-edit analysis by checking past mistakes, loop risks, and scope violations before an edit occurs. This is a read/query operation against stored session history and memory — it retrieves and evaluates information rather than modifying anything. The description says it's 'auto-run' by a hook but produces an impact assessment, not a write or destructive action.
From the tool's definition pre_edit_check ... Call manually only for an explicit impact check (past mistakes, loop risk, scope violations)
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs pre_edit_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Engram, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pre_edit_check, this is the rule to start with:
pre_edit_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Engram, apply this rule, and every pre_edit_check call is checked against it from then on.
Questions about pre_edit_check
RARELY NEEDED — the PreToolUse hook auto-runs this before every edit. Call manually only for an explicit impact check (past mistakes, loop risk, scope violations). It is categorised as a Read tool in the Claude Engram MCP Server, which means it retrieves data without modifying state.
Register the Claude Engram MCP server in PolicyLayer and add a rule for pre_edit_check: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Claude Engram. Nothing to install.
pre_edit_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pre_edit_check rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for pre_edit_check. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
pre_edit_check is provided by the Claude Engram MCP server (20alexl/claude-engram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Engram, and thousands of servers like it.
This server
Across the catalogue