Skip to main content
Glama

UAI x402 Security Tools

cloudflare-worker-security-review

Review Cloudflare Worker source and optional wrangler.toml for hardcoded secrets, unsafe CORS, missing admin auth, sensitive logging, and dynamic code execution. (REST equivalent: POST /api/v1/cloudflare-worker-security-review, $0.10)

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": {
      "workerCode": "<workerCode>"
    },
    "name": "cloudflare-worker-security-review"
  }
}

Input Schema

NameRequiredDescriptionDefault
workerCodeYesCloudflare Worker source code
wranglerTomlNoOptional wrangler.toml contents

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears most of the disclosure burden. It adds genuinely useful behavior context by labeling the operation a 'Review' (implying a non-mutating analysis) and disclosing the paid REST equivalent at $0.10 per call, which matters for cost-aware invocation. It does not say what the review returns, whether findings are scored/severity-ranked, or any limits on code size.

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?

Front-loaded single sentence naming the resource and the checks, followed by a short parenthetical with the REST endpoint and price. Both sentences earn their place; only minor tightening would improve it.

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

Completeness3/5

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

For a two-parameter, no-output-schema analysis tool with only a title annotation, the description should say more about what a caller gets back (finding list? severity? pass/fail?). The absence of an output schema makes that gap more consequential, though the input side is fully covered.

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 both parameters are already documented. The description only echoes that wranglerToml is optional and supplies no format, size, or snippet-vs-full-file guidance, so it adds little beyond the schema — 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?

States a specific verb ('Review') and resource ('Cloudflare Worker source and optional wrangler.toml') and enumerates the exact issue classes checked: hardcoded secrets, unsafe CORS, missing admin auth, sensitive logging, dynamic code execution. The 'Cloudflare Worker' scoping separates it from generic secret-scan or repo-wide tools, but it never names or contrasts a sibling such as wrangler-config-audit, which overlaps on the wrangler.toml side.

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 only implied by the checklist of findings the tool produces; there is no explicit statement of when to call this versus e.g. wrangler-config-audit or secret-scan, nor any prerequisite or exclusion. An agent can infer it is for reviewing Worker code before deploy, but must guess at 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