Switch operating mode (a, b, or c). Mode A: Local Guardian (zero LLM, EU AI Act full compliance). Mode B: Smart Local (local Ollama LLM, EU AI Act full). Mode C: Full Power (cloud LLM, best accuracy). Resets the engine to apply the new mode configuration. Args: mode: Target mode - 'a', 'b', or 'c'.
AI agents invoke set_mode to trigger actions in Qualixar/superlocalmemory. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool doesn't merely read or write data; it changes the operational mode of the memory system and resets the engine, which is an active execution of system reconfiguration. Misuse could switch from a privacy-compliant local mode (A/B) to a cloud-based mode (C), potentially exposing sensitive memory data to external cloud LLMs — a meaningful blast radius tied to privacy and compliance posture.
From the tool's definition 'Resets the engine to apply the new mode configuration' — switching modes triggers a system reconfiguration/reset of the running engine
Documented attack patterns abuse exactly the kind of access set_mode 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 set_mode:
{
"version": "1",
"default": "deny",
"tools": {
"set_mode": {
"limits": [
{
"counter": "set_mode_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}set_mode stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Switch operating mode (a, b, or c). Mode A: Local Guardian (zero LLM, EU AI Act full compliance). Mode B: Smart Local (local Ollama LLM, EU AI Act full). Mode C: Full Power (cloud LLM, best accuracy). Resets the engine to apply the new mode configuration. Args: mode: Target mode - 'a', 'b', or 'c'. It is categorised as a Execute tool in the Qualixar/superlocalmemory MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Qualixar/superlocalmemory MCP server in PolicyLayer and add a rule for set_mode: 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.
set_mode is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the set_mode 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 set_mode. 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.
set_mode 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.