Switch the active memory profile. All operations scope to this profile.
AI agents use switch_profile 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.
The tool changes system state by switching which memory profile is active, affecting the scope of subsequent operations. This is a Write-category action because it modifies configuration reversibly without permanently deleting data or executing arbitrary code.
From the tool's definition Tool description states it 'Switch[es] the active memory profile' with all operations scoping to the switched profile. This modifies the active state/configuration of the system, which is a reversible state change.
Documented attack patterns abuse exactly the kind of access switch_profile 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 switch_profile:
{
"version": "1",
"default": "deny",
"tools": {
"switch_profile": {
"limits": [
{
"counter": "switch_profile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}switch_profile 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.
Switch the active memory profile. All operations scope to this profile. 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 switch_profile: 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.
switch_profile 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 switch_profile 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 switch_profile. 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.
switch_profile 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.