Skip to main content
Glama
Shrike-Security

Shrike Security MCP Server

reset_session

Idempotent

Reset the session correlation engine to clear accumulated risk scores and turn history after false positives or security testing, allowing a clean start for new tasks within the current session.

Instructions

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoOptional reason for the reset (logged for audit purposes)
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses what is cleared (turn history, risk score), what is unaffected (other sessions, global patterns, scan results), and includes error handling (non-critical, scanning continues, session expires in 2 hours). Annotations already provide idempotentHint, but description adds significant behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with headers (WHEN TO USE, WHAT IT DOES, IMPORTANT, ERROR HANDLING). Every sentence adds value, no fluff. Concise yet comprehensive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description fully covers purpose, side effects, error handling, and idempotency. The tool's behavior is completely self-contained and clear for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single optional parameter 'reason' is fully described in the input schema (100% coverage). The description adds context about audit logging but does not improve on the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it resets the session-aware correlation engine state for the current session, clearly specifying the verb and resource. It distinguishes itself from sibling tools like scan_* and get_threat_intel by focusing on session state management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit WHEN TO USE bullet points (e.g., after resolving a flagged attack, starting a new logical task, false positive confirmation) and clarifies that individual scan results are unaffected, giving agents clear guidance on appropriate usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Shrike-Security/shrike-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server