Manage the explicit Core Memory pin set (v3.4.65). - pin: mark a fact as always-injected - unpin: clear the pin - list: return currently pinned facts
AI agents use core_memory to create or update resources in Qualixar/superlocalmemory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qualixar/superlocalmemory environment.
The tool primarily writes/modifies persistent memory state by pinning or unpinning facts (marking them as always-injected). The 'list' sub-operation is read-only, but the dominant capability is write (modifying which facts are pinned). Unpinning could be considered mildly destructive but is reversible since the underlying fact is not deleted.
From the tool's definition 'Manage the explicit Core Memory pin set' with operations: 'pin: mark a fact as always-injected', 'unpin: clear the pin', 'list: return currently pinned facts'
Documented attack patterns abuse exactly the kind of access core_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qualixar/superlocalmemory, and nothing reaches the server without passing your rules. This is the rule we recommend for core_memory:
{
"version": "1",
"default": "deny",
"tools": {
"core_memory": {
"limits": [
{
"counter": "core_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}core_memory 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.
Manage the explicit Core Memory pin set (v3.4.65). - pin: mark a fact as always-injected - unpin: clear the pin - list: return currently pinned facts. It is categorised as a Write tool in the Qualixar/superlocalmemory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Qualixar/superlocalmemory MCP server in PolicyLayer and add a rule for core_memory: 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 Qualixar/superlocalmemory. Nothing to install.
core_memory 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 core_memory 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 core_memory. 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.
core_memory is provided by the Qualixar/superlocalmemory MCP server (qualixar/superlocalmemory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Qualixar/superlocalmemory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Qualixar/superlocalmemory tools catalogued and risk-classified — across an index of 42,500+ MCP servers.