Skip to main content
Glama

BRAINIAC Application & Pipeline Security Checks

Analyse GCP IAM policy bindings

appsec-config_gcp-iam-binding-analyze
Read-onlyIdempotent

Flag basic roles, public members and service-account impersonation. Price $0.03 USDC. POST /api/v1/appsec-config/gcp-iam-binding-analyze. 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": {
      "policy": "<policy>"
    },
    "name": "appsec-config_gcp-iam-binding-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyYespolicy, object. Required.
serviceAccountPoliciesNoserviceAccountPolicies, object. Optional.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description earns credit for disclosing the commercial/transport behavior: $0.03 USDC cost, a POST endpoint, and that an unpaid call returns x402 payment terms without executing. It does not, however, describe what the analysis emits or any limits on policy size, so the value added is real but narrow.

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?

Three compact sentences with the functional purpose front-loaded, followed by cost and transport details. Every sentence carries information, though the telegraphic 'Price $0.03 USDC.' and the raw route read more like doc fragments than prose.

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, and the nested policy/bindings shape is fully described in the input schema, so the description need not restate either. It closes the remaining gap an agent would otherwise hit — that calls are paid and that an unpaid attempt is a no-op returning payment terms — which is exactly the kind of non-schema information that belongs here.

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 both 'policy' and 'serviceAccountPolicies' including required/optional status. The description adds no meaning about the shape of bindings entries, role string formats, or how serviceAccountPolicies interacts with the policy field. Baseline 3 applies.

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 names a specific verb ('Flag') and enumerates the exact findings produced: basic roles, public members and service-account impersonation. Combined with the title, an agent can tell this audits GCP IAM policy bindings rather than AWS policies or other appsec artifacts. It stops short of restating the resource being analyzed inside the description body, but the intent is unambiguous.

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 reach for this tool versus siblings such as appsec-config_aws-iam-policy-analyze, nor any prerequisites about supplying an existing policy document. The only usage-adjacent statement is the payment precondition, which concerns billing rather than tool selection.

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