Manually link an SLM memory to a code graph node. BRIDGE TOOL: Creates an explicit link between a memory and a code entity. Args: fact_id: The SLM atomic fact ID. code_entity: Function/class/file qualified name or partial name. link_type: One of: mentions, decision_about, bug_fix, refactor, desig...
AI agents use link_memory_to_code 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.
This tool creates a new link/relationship between an existing memory fact and a code graph node. It is a reversible write operation (creating an association), not executing code, deleting data, or involving financial transactions. Severity is low because it only creates metadata linkages within a local memory system with no external side effects.
From the tool's definition 'Creates an explicit link between a memory and a code entity' — establishes a new association/relationship between existing records
Documented attack patterns abuse exactly the kind of access link_memory_to_code 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 link_memory_to_code:
{
"version": "1",
"default": "deny",
"tools": {
"link_memory_to_code": {
"limits": [
{
"counter": "link_memory_to_code_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}link_memory_to_code 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.
Manually link an SLM memory to a code graph node. BRIDGE TOOL: Creates an explicit link between a memory and a code entity. Args: fact_id: The SLM atomic fact ID. code_entity: Function/class/file qualified name or partial name. link_type: One of: mentions, decision_about, bug_fix, refactor, design_rationale. 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 link_memory_to_code: 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.
link_memory_to_code 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 link_memory_to_code 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 link_memory_to_code. 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.
link_memory_to_code 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.