Incrementally update the code graph for changed files. If changed_files is empty, auto-detects changes via git diff HEAD~1. Args: repo_path: Absolute path to repository root. Empty = use last built repo. changed_files: Comma-separated file paths (relative to repo root).
AI agents use update_code_graph 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 or modifies data reversibly by updating a code graph representation. It does not delete data (would be Destructive), does not execute arbitrary code with unpredictable side effects (would be Execute), and does not destroy information irreversibly. The update is metadata-level within a memory system.
From the tool's definition Tool description uses 'update' and 'incrementally update the code graph', indicating modification of an existing data structure (the code graph). The tool modifies internal memory/metadata about code structure.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access update_code_graph 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 update_code_graph:
{
"version": "1",
"default": "deny",
"tools": {
"update_code_graph": {
"limits": [
{
"counter": "update_code_graph_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_code_graph 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.
Incrementally update the code graph for changed files. If changed_files is empty, auto-detects changes via git diff HEAD~1. Args: repo_path: Absolute path to repository root. Empty = use last built repo. changed_files: Comma-separated file paths (relative to repo root). 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 update_code_graph: 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.
update_code_graph 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 update_code_graph 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 update_code_graph. 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.
update_code_graph 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.