Resets the session-aware correlation engine (Layer 9) state for the current session. WHEN TO USE: - After resolving a flagged multi-turn attack pattern (e.g., topic_pivot false positive) - When starting a new logical task within the same MCP session - After a user confirms that flagged content w...
Part of the Shrike Security MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call reset_session to permanently remove or destroy resources in Shrike Security. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call reset_session in a loop, permanently destroying resources in Shrike Security. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
reset_session:
rules:
- action: deny
reason: "Blocked by default — enable with approval"See the full Shrike Security policy for all 12 tools.
Agents calling destructive-class tools like reset_session have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
reset_session is one of the critical-risk operations in Shrike Security. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
Resets the session-aware correlation engine (Layer 9) state for the current session. WHEN TO USE: - After resolving a flagged multi-turn attack pattern (e.g., topic_pivot false positive) - When starting a new logical task within the same MCP session - After a user confirms that flagged content was a false positive - When session trajectory has accumulated risk from legitimate security testing WHAT IT DOES: - Clears the accumulated turn history and risk score for this session - Future scans start with a clean session trajectory - Does NOT affect other sessions or global threat patterns IMPORTANT: This only resets the correlation state. Individual scan results are unaffected — a prompt injection will still be blocked regardless of session state. ERROR HANDLING: If this tool fails, it is non-critical. Scanning continues normally. The session will eventually expire on its own (2 hour TTL).. It is categorised as a Destructive tool in the Shrike Security MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for reset_session. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Shrike Security MCP server.
reset_session is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reset_session rule in your Intercept 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 Intercept policy for 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.
reset_session is provided by the Shrike Security MCP server (shrike-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept