Skip to main content
Glama
Sign In
llm-toolkit

llm-toolkit

by 0x1Jar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Bypass Waf

bypass-waf

Generate WAF-specific bypass variants for payloads to evade Cloudflare, ModSecurity, AWS WAF, or generic protections.

Instructions

Generate WAF-specific bypass variants for a payload (cloudflare, modsecurity, aws-waf, generic)

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": "bypass-waf"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
wafTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description must disclose all behavioral traits. It only states the tool generates bypass variants, omitting information about whether it is destructive, requires special permissions, or has rate limits. The agent gains little actionable insight beyond the basic function.

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?

The description is a single, focused sentence that front-loads the key action and resource. Every word provides value, with no redundancy or filler.

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 simple (two parameters, no output schema), but the description fails to cover essential context: return value format, relationship to sibling tools, or any side effects. It leaves the agent unprepared to interpret results or choose this tool appropriately.

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%, so the description must compensate. It lists the WAF types (which match the enum) but does not explain the 'payload' parameter's expected format, constraints, or how it relates to the WAF types. The addition is minimal and insufficient for an agent to use parameters correctly without guessing.

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 clearly states the tool generates WAF-specific bypass variants for a payload and lists the supported WAF types (cloudflare, modsecurity, aws-waf, generic). This provides a specific verb-resource pairing, but it does not differentiate from the sibling tool 'generate-payload', which might serve a similar purpose.

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?

No guidance is provided on when to use this tool versus alternatives such as 'generate-payload' or 'analyze-payload'. The description does not include context about prerequisites, expected scenarios, or exclusions.

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