Skip to main content
Glama

UAI x402 Security Tools

policy-genie

Validate AWS IAM and Cloudflare Zero Trust policy JSON for risky wildcards, bypass rules, weak scoping, and embedded secrets. (REST equivalent: POST /api/v1/validate-policy, $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": {
      "rawPolicyText": "<rawPolicyText>"
    },
    "name": "policy-genie"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawPolicyTextYesIAM or Cloudflare Access policy JSON

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 does the work: it discloses the check categories and a pricing/transport detail (POST /api/v1/validate-policy, $0.05), which is genuinely useful context not in structured fields. However, it never states that the call is non-mutating/read-only, nor what the findings look like, leaving meaningful behavioral gaps for a tool with zero annotation coverage.

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?

Two sentences, front-loaded with purpose and the check list, with the REST/pricing parenthetical kept short. The parenthetical is slightly tangential but is real information, not padding.

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 one-parameter validator with no output schema, the definition covers the input and the checks but says nothing about the response shape (findings, severity, pass/fail) an agent would need to act on the result. Adequate to invoke, incomplete to interpret.

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% and the single parameter rawPolicyText is already documented as "IAM or Cloudflare Access policy JSON". The description adds no format, size, encoding, or example detail beyond that, so the baseline of 3 applies.

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?

Specific verb ("Validate") plus precise resource ("AWS IAM and Cloudflare Zero Trust policy JSON"), and it enumerates what is being checked: risky wildcards, bypass rules, weak scoping, embedded secrets. This distinguishes it from sibling scanners like iam-risk-score or terraform-iam-risk-scan, which operate on repos/configs rather than a pasted policy document.

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 input type sharply implies when to use it (you have a policy JSON blob to check), but there is no explicit when-to-use/when-not statement and no routing to alternatives such as iam-risk-score or terraform-iam-risk-scan. Guidance is inferable 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