Skip to main content
Glama

BRAINIAC Payload Safety & Architecture Control Checks

Detect trust-boundary violations

security_trust-boundary-violation-detect
Read-onlyIdempotent

Find caller-supplied data flows that cross from a higher trust zone to a lower one without the required controls. Uses only supplied components, zones, flows, and controls. No infrastructure is scanned. Price $0.04 USDC. POST /api/v1/security/trust-boundary-violation-detect. 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>"
    },
    "name": "security_trust-boundary-violation-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowsYesflows, array. Required.
zonesYeszones, array. Required.
controlsNocontrols, array. Optional.
componentsYescomponents, array. Required.
required_controls_on_trust_dropNorequired controls on trust drop, array. Optional.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuinely useful context beyond that: a $0.04 USDC price, the POST /api/v1/... endpoint, and critically that an unpaid call returns x402 payment terms and does not execute — a behavioral trait an agent cannot get from 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?

Four short sentences, front-loaded with the core purpose, then scope, then cost and transport details. 'No infrastructure is scanned' partially restates the preceding 'uses only supplied...' sentence, but the remaining content is practical rather than filler.

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

Completeness5/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 annotations cover the safety profile. The description supplies what structured fields cannot: the data-only input model, the payment requirement, and the failure behavior of an unpaid call. Nothing an agent needs to invoke it correctly appears missing.

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 nested components/zones/flows/controls parameters are already documented field-by-field. The description only adds a high-level statement that analysis uses only the supplied inputs, without explaining semantics such as how trust_level ordering drives a violation. Baseline 3 is appropriate.

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 specific verb and resource ('Find caller-supplied data flows that cross from a higher trust zone to a lower one without the required controls'), which is far more informative than the tool name alone. It does not explicitly name or contrast with siblings like security_sensitive-data-flow-audit, so the boundary with that closest neighbor is left to inference.

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?

Implicitly conveys context via 'Uses only supplied components, zones, flows, and controls' and 'No infrastructure is scanned,' which tells the agent this is a model-based analysis over caller-provided data rather than a live scan. However, there is no explicit when-to-use vs when-not-to-use guidance and no reference to the sibling tools as alternatives.

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