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 wa...
Part of the Shrike Security server.
Free to start. No card required.
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. PolicyLayer 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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"hide": [
"reset_session"
]
}See the full Shrike Security policy for all 12 tools.
These attack patterns abuse exactly the kind of access reset_session gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
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.
Register the Shrike Security MCP server in PolicyLayer and add a rule for 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 Shrike Security. Nothing to install.
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 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 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Shrike Security tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.