Skip to main content
Glama

BRAINIAC Identity & Access Security

Detect session-hijacking signals

identity-security_session-hijacking-signal-detect

Identify suspicious session changes and reuse patterns from caller-supplied session, device, IP, and user-agent fields. Indicators only—not confirmed hijacking. Price $0.04 USDC. POST /api/v1/identity-security/session-hijacking-signal-detect. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "identity-security_session-hijacking-signal-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
eventsNo
accountsNo
policiesNo
dormantDaysNo
maxTravelKmhNo
mfaPushThresholdNo
mfaWindowMinutesNo
authWindowMinutesNo
sharingWindowHoursNo
serviceBaselineWindowHoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful traits: paid operation at $0.04 USDC, POST transport, 402 rejection for unpaid calls, and an explicit 'indicators only — not confirmed hijacking' caveat about result interpretation. It omits other behavioral facts an agent needs with zero annotation coverage, such as whether any input is mandatory, what happens with empty/insufficient events, and what the response contains.

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

Conciseness4/5

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

Three short sentences, front-loaded with the core purpose and the disclaimer before the billing/endpoint details. The pricing and route sentences are arguably transport metadata, but they are stated compactly without padding.

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

Completeness2/5

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

This is a high-complexity tool (16 params, nested objects, no output schema, no annotations), yet the description never says which inputs are required to produce a result, how thresholds affect detection, or what the indicator output looks like. For a detector whose entire value is interpreting returned indicators, that leaves material gaps.

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

Parameters2/5

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

Schema description coverage is 0% across 16 parameters, including nested events/accounts/policies objects, so the description was required to compensate and largely does not. Mentioning 'session, device, IP, and user-agent fields' loosely maps to a few event properties, but the seven threshold parameters (dormantDays, maxTravelKmh, mfaPushThreshold, authWindowMinutes, etc.) and the csv/json/text/file carrier options are unexplained.

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

Purpose4/5

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

States a specific verb and target ('Identify suspicious session changes and reuse patterns') and narrows the evidence to 'session, device, IP, and user-agent fields', which is distinguishable from siblings like impossible-travel or mfa-fatigue. It stops short of explicitly differentiating itself by name, so a 4 rather than a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no comparison to the many sibling detectors. The only implicit signal is the mention of session/device/IP/user-agent fields, which hints at the data to supply but not the conditions that select this tool over alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources