Skip to main content
Glama

BRAINIAC Application & Pipeline Security Checks

Audit CloudFormation templates

appsec-config_cloudformation-audit
Read-onlyIdempotent

Flag public storage, open security groups, missing encryption and wildcard IAM. Price $0.04 USDC. POST /api/v1/appsec-config/cloudformation-audit. An unpaid call returns the x402 payment terms and does 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": {
      "template": "<template>"
    },
    "name": "appsec-config_cloudformation-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateYestemplate, string, length 0 to 5000000. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
findingsNofindings. Array.
unresolvedNounresolved. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful non-annotation behavior: the exact price ($0.04 USDC) and, critically, that an unpaid call returns x402 payment terms without executing — an agent needs this to interpret an empty result correctly. It stops short of noting any limits on template size or runtime.

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?

Four short sentences with no filler: findings first, then price, then endpoint, then the payment-failure caveat. Front-loading the detection scope before the billing details is the right ordering.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and the single input is fully documented by the schema. The description covers the payment/billing behavior that the structured fields cannot express. Only the accepted template serialization format is left unstated.

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% for the single 'template' parameter, so the baseline applies. The description adds no meaning beyond the schema — notably it does not say whether the template should be JSON or YAML, which is the one ambiguity an agent would actually hit.

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 uses a specific verb ('Flag') and enumerates concrete findings — public storage, open security groups, missing encryption, wildcard IAM — which clearly signals a static misconfiguration audit. It never states the resource being audited in the description text itself (CloudFormation templates only appear in the name/title), so it is slightly short of fully self-contained differentiation from siblings like aws-iam-policy-analyze.

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?

There is no guidance on when to choose this over the many sibling auditors (nginx-config-audit, openapi-security-audit, aws-iam-policy-analyze, etc.), nor any prerequisite or exclusion. The only conditional behavior mentioned is payment-related, not usage-related.

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