Get the complete memory timeline for a code entity. BRIDGE TOOL: Shows all memories about a function/class ordered by time. Args: code_entity: Function/class/file name or qualified name.
AI agents call code_entity_history to retrieve information from Qualixar/superlocalmemory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval tool that queries a persistent memory store to fetch historical information about code entities. It has no side effects—it only reads and returns timeline data sorted temporally.
From the tool's definition Tool retrieves and queries existing memory data ('Get the complete memory timeline', 'Shows all memories... ordered by time'). No modification, deletion, or execution of code indicated.
Documented attack patterns abuse exactly the kind of access code_entity_history 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 code_entity_history:
{
"version": "1",
"default": "deny",
"tools": {
"code_entity_history": {}
}
}code_entity_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the complete memory timeline for a code entity. BRIDGE TOOL: Shows all memories about a function/class ordered by time. Args: code_entity: Function/class/file name or qualified name. It is categorised as a Read tool in the Qualixar/superlocalmemory MCP Server, which means it retrieves data without modifying state.
Register the Qualixar/superlocalmemory MCP server in PolicyLayer and add a rule for code_entity_history: 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.
code_entity_history 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 code_entity_history 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 code_entity_history. 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.
code_entity_history 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.