Creates or updates a named system/coding pattern (e.g.,
AI agents use log_system_pattern to create or update resources in Engrams — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Engrams environment.
The tool explicitly creates or updates data (system/coding patterns) in persistent memory. This is a reversible write operation — patterns can be updated or deleted. The sibling tool 'delete_item' suggests deletions are handled separately, confirming this tool only writes/modifies. Severity is medium because misuse could pollute the AI's persistent context with incorrect patterns, affecting future behavior.
From the tool's definition Creates or updates a named system/coding pattern
Documented attack patterns abuse exactly the kind of access log_system_pattern gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Engrams, and nothing reaches the server without passing your rules. This is the rule we recommend for log_system_pattern:
{
"version": "1",
"default": "deny",
"tools": {
"log_system_pattern": {
"limits": [
{
"counter": "log_system_pattern_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}log_system_pattern stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Creates or updates a named system/coding pattern (e.g.,. It is categorised as a Write tool in the Engrams MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Engrams MCP server in PolicyLayer and add a rule for log_system_pattern: 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 Engrams. Nothing to install.
log_system_pattern is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the log_system_pattern 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 log_system_pattern. 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.
log_system_pattern is provided by the Engrams MCP server (stevebrownlee/engrams). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Engrams, 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.
42 Engrams tools catalogued and risk-classified — across an index of 43,000+ MCP servers.