Skip to main content
Glama

BRAINIAC Payload Safety & Architecture Control Checks

Audit sensitive data flows

security_sensitive-data-flow-audit
Read-onlyIdempotent

Check where caller-declared sensitive data classes travel through supplied components and whether handling rules for zones, components, and required controls are violated. No repository is scanned. Price $0.04 USDC. POST /api/v1/security/sensitive-data-flow-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": {
      "components": "<components>",
      "zones": "<zones>",
      "flows": "<flows>",
      "handling_rules": "<handling_rules>",
      "sensitive_data_classes": "<sensitive_data_classes>"
    },
    "name": "security_sensitive-data-flow-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowsYesflows, array. Required.
zonesYeszones, array. Required.
controlsNocontrols, array. Optional.
componentsYescomponents, array. Required.
handling_rulesYeshandling rules, array. Required.
sensitive_data_classesYessensitive data classes, array. Required.

Output Schema

NameRequiredDescriptionDefault
summaryNosummary. Object.
findingsNofindings. Array.
explanationsNoexplanations. Array.
sensitive_flowsNosensitive_flows. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, and the description adds material context beyond them: the tool performs no repository scanning, costs $0.04 USDC, is invoked via POST, and an unpaid call returns x402 payment terms without running. That payment-gating behavior is exactly the kind of trait an agent needs and cannot get from the annotations.

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?

The purpose is front-loaded in the first sentence, followed by the scope caveat, price, endpoint, and payment behavior. Four short sentences with little waste, though the raw endpoint path is the least valuable element and borders on transport detail.

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?

For a six-parameter tool with a deeply nested input schema and an existing output schema, the description covers the essential non-obvious facts: no scanning, cost, and payment gating. Return values need not be explained because an output schema exists; only cross-parameter semantics remain unaddressed.

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 description coverage is 100%, so the schema already documents all six parameters, including nested flow, zone, control, component, and handling-rule fields. The description adds only framing ("caller-declared sensitive data classes," "supplied components") without explaining relationships such as how control_ids link to controls or how handling rules are matched.

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 gives a specific verb and resource: check where caller-declared sensitive data classes travel across supplied components and whether handling rules for zones, components, and required controls are violated. It is substantively distinct from the sibling audits (payload anomaly scoring, control coverage gaps, trust boundary violations), though it never names an alternative to route against 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?

"No repository is scanned" usefully tells the agent this is pure analysis over supplied input rather than a scanner, and the payment note tells it an unpaid call will not execute. However, there is no explicit when-to-use/when-not guidance relative to the sibling security audits, so selection guidance is only implied.

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