Skip to main content
Glama
Sign In
Sandbox Code Auditor MCP

Sandbox Code Auditor MCP

by Whambammy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

regex_redos_exponential_scanner

Detects catastrophic polynomial and exponential backtracking (ReDoS) in regular expressions using NFA/DFA cycle decomposition to prevent denial-of-service attacks.

Instructions

Audits regular expressions for catastrophic polynomial and exponential backtracking (ReDoS) vulnerabilities using NFA/DFA cycle decomposition. (0.035 USDC on Base L2)

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": {
      "payload": "<payload>"
    },
    "name": "regex_redos_exponential_scanner"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesInput parameters or JSON string payload for the tool execution
paymentSignatureNoBase L2 USDC micropayment signature or transaction hash for x402 settlement

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations, so description carries the burden. It discloses the method (NFA/DFA cycle decomposition) and cost (0.035 USDC on Base L2), but does not describe the output format or any side effects or prerequisites. It adds some value but lacks critical behavioral details like return value.

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?

One sentence plus cost note. Efficient and 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?

Given the tool's complexity and lack of output schema, the description is incomplete. It does not specify what the payload should contain (e.g., the regex) or what the tool returns. Missing critical usage context.

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 coverage is 100%, so baseline is 3. The description does not add any parameter semantics; the payload description is generic and the description does not clarify what to pass. It doesn't compensate for the vague schema.

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 (audits) and resource (regular expressions) with a specific vulnerability type (ReDoS). Distinguishes from siblings like generate_regex_dfa by focusing on vulnerability scanning rather than DFA generation.

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?

The description implies usage for auditing regexes for ReDoS but does not explicitly compare with alternatives or state when not to use. There is no mention of exclusions or alternative tools, so guidance is limited.

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

Deploy Server

Other Tools