Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_prowler

Destructive

Runs Prowler security assessments inside the engagement workspace using direct argument passing, avoiding shell parsing and keeping artifact paths relative.

Instructions

Run prowler from the OpenCyber cloud container iac toolkit. The container executes prowler 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_prowler"
  }
}

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.7/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, so the safety profile is covered by structured fields. The description adds context those fields cannot express: there is no shell parsing, which is a security-relevant execution detail, and execution is scoped to a specific engagement namespace. It could go further by explaining what destructive effects or network activity the scan may produce.

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 short sentences, front-loaded with the core action and followed by the execution semantics and path guidance. Every sentence carries useful information with no redundant restatement of the name or annotations. Slightly denser wording would have allowed mention of the unused `stdin` parameter without bloat.

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 not be explained, and the annotations cover the risk profile. For a four-parameter tool that wraps an external binary, the description supplies the essential mechanics: argv passthrough, no shell interpretation, and namespace scope. The only real gap is the unaddressed `stdin` parameter.

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 bears full responsibility for explaining all four parameters. It meaningfully clarifies `arguments` as argv tokens and explains the engagement namespace scope and the relative-path expectation for `working_directory`. However, `stdin` is never mentioned, and the format of `engagement_id` is left to inference.

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: it runs the `prowler` scanner from the OpenCyber container iac toolkit, and it executes that binary directly with the supplied argv tokens. This is clear enough that an agent knows exactly which external tool is being invoked. It does not explicitly contrast itself with sibling tools such as oc_bash or oc_amass, but naming `prowler` and the 'iac toolkit' scope provides meaningful differentiation.

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?

The description implies when and how to use the tool: it tells the agent to pass argv tokens rather than a shell string, to operate within the selected engagement namespace, and to use relative paths for engagement artifacts. These are practical invocation constraints. It never states when to prefer this over an alternative or what prerequisites, such as a required engagement context, must exist before calling it.

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