Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_terrascan

Destructive

Run Terrascan scans on infrastructure-as-code in an engagement workspace to detect cloud misconfigurations using supplied arguments and relative artifact paths.

Instructions

Run terrascan from the OpenCyber cloud container iac toolkit. The container executes terrascan directly with the supplied argv tokens; shell parsing is never used. Runs from the selected engagement namespace; use relative paths for engagement artifacts.

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": {
      "engagement_id": "<engagement_id>",
      "arguments": "<arguments>"
    },
    "name": "oc_terrascan"
  }
}

Input Schema

NameRequiredDescriptionDefault
stdinNo
argumentsYes
engagement_idYes
working_directoryNo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, and idempotentHint=false. The description adds meaningful execution behavior beyond that: terrascan receives argv tokens directly, shell parsing is never used, execution is scoped to the engagement namespace, and artifacts should use relative paths.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tight sentences, front-loaded with the purpose and then operational constraints. Every sentence adds useful information with no filler.

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?

The output schema covers return values and the annotations cover safety characteristics, but with zero schema descriptions the description should explain all four parameters. It leaves stdin unexplained and does not provide selection guidance among sibling tools.

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 0%, so the description must carry parameter meaning. It clarifies that arguments are argv tokens, engagement_id selects the namespace, and working_directory should use relative paths for engagement artifacts, but it does not explain stdin or the required argument format.

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 executable, terrascan, and its execution context in the OpenCyber cloud container iac toolkit, so the agent can tell this is a terrascan runner rather than a generic shell. It does not explain what terrascan scans or explicitly differentiate it from sibling security tools, so it stops short of a 5.

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?

The description gives operational advice about using relative paths, but provides no when-to-use or when-not-to-use guidance and names no alternative such as oc_bash or another scanner. An agent must infer tool selection on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools