clear_scoped_memory

Clear all stored memories for a session

Server consciousness MCP server one710/consciousness
Category Destructive
Risk class Critical
Parameters 00 required

What clear_scoped_memory does on consciousness MCP server

AI agents call clear_scoped_memory to permanently remove resources in consciousness MCP server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why clear_scoped_memory needs a policy

This tool permanently deletes session-scoped memory data without a recovery mechanism. While the blast radius is limited to session-scoped memories (not universal), the operation is inherently destructive and irreversible. An AI agent misusing this could lose critical context or user information for an entire session.

From the tool's definition Tool name 'clear_scoped_memory' and description 'Clear all stored memories for a session' indicate irreversible deletion of data. The verb 'clear' combined with 'all stored memories' describes a bulk erasure operation that cannot be undone.

Risk signalsBulk/mass operation — affects multiple targets

Questions about clear_scoped_memory

What does the clear_scoped_memory tool do? +

Clear all stored memories for a session. It is categorised as a Destructive tool in the consciousness MCP server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_scoped_memory? +

Register the consciousness MCP server MCP server in PolicyLayer and add a rule for clear_scoped_memory: 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 consciousness MCP server. Nothing to install.

What risk level is clear_scoped_memory? +

clear_scoped_memory is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_scoped_memory? +

Yes. Add a rate_limit block to the clear_scoped_memory 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.

How do I block clear_scoped_memory completely? +

Set action: deny in the PolicyLayer policy for clear_scoped_memory. 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.

What MCP server provides clear_scoped_memory? +

clear_scoped_memory is provided by the consciousness MCP server MCP server (one710/consciousness). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.