Get memory usage breakdown by fact type and lifecycle state.
AI agents call memory_used 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 tool retrieves and reports memory usage statistics. It performs no writes, deletions, code execution, or financial operations. The operation is purely observational—reading internal state metrics about memory consumption. The blast radius of misuse is minimal: an agent could at worst spam queries, but cannot affect data or system state beyond consuming computational resources.
From the tool's definition Tool name 'memory_used' and description 'Get memory usage breakdown by fact type and lifecycle state' indicate a query operation that retrieves metrics without modification or side effects.
Documented attack patterns abuse exactly the kind of access memory_used 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 memory_used:
{
"version": "1",
"default": "deny",
"tools": {
"memory_used": {}
}
}memory_used 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 memory usage breakdown by fact type and lifecycle state. 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 memory_used: 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.
memory_used 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 memory_used 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 memory_used. 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.
memory_used 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.