Skip to main content
Glama

BRAINIAC GraphQL Federation Security

Audit federation authorization

graphql-security_federation-authorization-audit

Compare @authenticated, @requiresScopes, @policy, and caller-defined authorization directives across supplied subgraph SDL. @requires, @key, @external, @provides, and @shareable are inspected for schema-level differences. audit_status is clean, findings_detected, invalid, or incomplete. risk_level is low, medium, high, or critical. A difference is not a runtime authorization result. No gateway is contacted. Price $0.05 USDC. POST /api/v1/graphql-security/federation-authorization-audit. Unpaid calls return 402 and do not run.

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": {
      "subgraphs": "<subgraphs>"
    },
    "name": "graphql-security_federation-authorization-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
expectedNo
subgraphsYes
supergraphNo
authorizationDirectivesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it enumerates the audit_status values (clean, findings_detected, invalid, incomplete), the risk_level values, discloses that no gateway is contacted, that no runtime authorization is exercised, and that unpaid calls return 402 without executing. It does not describe the shape of findings or how many are returned, which keeps it short of a 5.

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?

Dense and front-loaded: the comparison scope comes first, then result enums, then caveats and operational terms. Sentences are short and each carries information, though the price/endpoint/402 sentences are operational detail rather than guidance.

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 four-parameter, no-annotation, no-output-schema tool, the description covers outcomes and constraints well but leaves the inputs underspecified. An agent could not confidently construct an `expected` element or know when to supply `supergraph` versus `subgraphs` from this text alone.

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% across four parameters, so the description must compensate and largely does not. It never explains the `expected` baseline array, the `supergraph` input, `federationVersion`, or the structure of `authorizationDirectives` beyond naming the directive semantics; only the `subgraphs`/SDL input is indirectly implied by "supplied subgraph SDL."

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 concrete verb and resource: "Compare @authenticated, @requiresScopes, @policy, and caller-defined authorization directives across supplied subgraph SDL," plus a secondary scope covering @requires/@key/@external/@provides/@shareable. The tool's domain (federation authorization directive parity) is distinctive enough to separate it from siblings like field-authorization-coverage, but no sibling is named explicitly.

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 scope statement; there is no explicit "use this when..." or "do not use for..." guidance, and no alternative is named. The caveat that "a difference is not a runtime authorization result" and "no gateway is contacted" helps an agent decide when this tool is inappropriate, but that is a boundary rather than positive routing guidance.

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