Skip to main content
Glama

BRAINIAC Identity & Access Security

Detect MFA fatigue

identity-security_mfa-fatigue-detect

Detect repeated MFA push/challenge patterns from caller-supplied MFA events that may indicate an MFA fatigue attack. Not confirmation of account takeover. Price $0.04 USDC. POST /api/v1/identity-security/mfa-fatigue-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_mfa-fatigue-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

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful operational facts (price, POST endpoint, 402 on unpaid calls with no execution) and frames the result as indicative rather than conclusive. However, it omits what minimum input is required, whether call history persists, rate limits, and any hint at the response shape for a nested-input analytic tool.

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?

Four short sentences, each with distinct content: what it detects, the interpretive caveat, the price, and the endpoint/payment behavior. No filler or repetition; slightly mechanical ordering but well front-loaded.

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?

The tool is complex (nested file/event/account/policy objects, 16 optional parameters, no output schema) and the description addresses only the conceptual purpose and billing mechanics. An agent would still not know what data it must supply or how to read the output, which is a substantial gap for a detection tool with a caveated verdict.

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?

With 16 parameters and 0% schema description coverage, the description should carry parameter meaning, but it names none. It only gestures at 'MFA events', leaving detection knobs like mfaPushThreshold, mfaWindowMinutes, asOf, and the required-vs-optional relationship between events/files opaque and unguessable.

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?

States a specific verb and resource ('Detect repeated MFA push/challenge patterns') plus the data source ('caller-supplied MFA events') and the threat it targets ('MFA fatigue attack'). The scope caveat 'Not confirmation of account takeover' further pins down what the output means, distinguishing it from broader siblings like authentication-pattern-analyze.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer it should supply MFA events data, and the 'not confirmation of account takeover' note hints at when the result is decisive. There is no explicit when-to-use vs. when-not guidance, no named alternative siblings, and no statement of prerequisites for the input data.

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