Skip to main content
Glama

UAI x402 Security Tools

cloudflare-zero-trust-audit

Analyze Cloudflare Zero Trust Access policy JSON for bypass rules, allow-everyone patterns, and weak identity constraints. (REST equivalent: POST /api/v1/cloudflare-zero-trust-audit, $0.05)

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": {
      "policyText": "<policyText>"
    },
    "name": "cloudflare-zero-trust-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyTextYesCloudflare Zero Trust Access policy JSON

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 the burden, and it does add useful operational facts beyond structured data: a REST equivalent endpoint and a $0.05 per-call cost. It says nothing about whether the input is transmitted externally, what the response contains, or how findings are structured, which leaves real gaps for an audit tool.

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?

Two sentences, front-loaded with the core action and the exact checks performed, with pricing and the REST mapping isolated in parentheses. Nothing is redundant or padded.

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?

With no output schema, the description should hint at what the analysis returns (finding list, severities, bypass counts), and it does not. For a one-parameter read-only audit tool that is a modest but noticeable omission rather than a blocking one.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents policyText as Cloudflare Zero Trust Access policy JSON. The description repeats that framing without adding format details, size limits, or example shapes, so 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 ("Analyze") and resource ("Cloudflare Zero Trust Access policy JSON") and even enumerates the defect classes it hunts for: bypass rules, allow-everyone patterns, weak identity constraints. It does not explicitly differentiate itself from siblings like cloudflare-worker-security-review, but the domain is narrow enough that confusion is unlikely.

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: it is clear you should pass an Access policy JSON document, but there is no statement of when to reach for this versus the adjacent Cloudflare or IAM audit tools, and no prerequisites or exclusions (e.g., what policy shapes are accepted).

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