mittwald_context_reset_session

Reset (clear) all user context parameters in Redis session (session-aware, multi-tenant safe)

Server Mittwald MCP Server mittwald/mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What mittwald_context_reset_session does on Mittwald MCP Server

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

Why mittwald_context_reset_session needs a policy

Clearing/resetting all user context parameters is a destructive operation that cannot be undone and removes stored session data. While the description notes it is 'session-aware, multi-tenant safe,' the action itself is irreversible data destruction. This exceeds Write (which is reversible modification) and qualifies as Destructive due to the clearing/erasure semantics.

From the tool's definition Tool name contains 'reset' and description states 'Reset (clear) all user context parameters' — this irreversibly wipes session state data from Redis.

Risk signalsBulk/mass operation — affects multiple targets

Questions about mittwald_context_reset_session

What does the mittwald_context_reset_session tool do? +

Reset (clear) all user context parameters in Redis session (session-aware, multi-tenant safe). It is categorised as a Destructive tool in the Mittwald 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 mittwald_context_reset_session? +

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

What risk level is mittwald_context_reset_session? +

mittwald_context_reset_session 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 mittwald_context_reset_session? +

Yes. Add a rate_limit block to the mittwald_context_reset_session 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 mittwald_context_reset_session completely? +

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

mittwald_context_reset_session is provided by the Mittwald MCP Server MCP server (mittwald/mcp-server). 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.