Skip to main content
Glama

BRAINIAC Application & Pipeline Security Checks

Detect ReDoS risk in a regular expression

appsec-config_regex-redos-check
Read-onlyIdempotent

Check a JavaScript regex for catastrophic backtracking with recheck. Price $0.02 USDC. POST /api/v1/appsec-config/regex-redos-check. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pattern": "<pattern>"
    },
    "name": "appsec-config_regex-redos-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagsNoflags, string, length 0 to 16. Required.
flavourNoflavour, string, one of javascript. Required.javascript
patternYespattern, string, length 0 to 2000. Required.

Output Schema

NameRequiredDescriptionDefault
attackNoattack. Object.
engineNoengine. String.
statusNostatus. String.
checkerNochecker. String.
sourcesNosources. Array.
complexityNocomplexity. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: a $0.02 USDC price, the POST endpoint, and the crucial detail that an unpaid call returns x402 payment terms without executing — information an agent cannot get from annotations or schema.

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 action and followed by the payment and endpoint facts. The raw path 'POST /api/v1/appsec-config/regex-redos-check' is arguably redundant for an agent that only calls the tool, but it is compact and does not bury the key information.

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?

With annotations covering safety, a full-coverage schema, and an output schema that handles return values, the description needs only to add what is missing — and it does, disclosing the payment requirement and the unpaid-call behavior. Nothing an agent needs to invoke it correctly is absent.

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?

Schema description coverage is 100%, so pattern, flags and flavour are already documented with types, lengths and the javascript enum. The description adds only that the target is a JavaScript regex, which is consistent with the single-value enum but not meaningfully beyond it. Baseline 3 applies.

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?

The description states a specific verb and resource ('Check a JavaScript regex for catastrophic backtracking with recheck'), which is precise and clearly distinct from the config-audit and scan siblings. It stops short of explicitly naming when a sibling tool would be preferable, so it is clear but not sibling-routing.

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 by the narrow scope ('JavaScript regex' for 'catastrophic backtracking'), which tells an agent what input this tool is for. There is no explicit when-to-use/when-not-to-use guidance or comparison to alternatives, so it remains implied rather than stated.

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