Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_exploit_search

Destructive

Searches local exploit databases for known vulnerabilities and proof-of-concept code using supplied keywords or CVE terms, helping identify relevant exploits during authorized security assessments.

Instructions

Run exploit search from the OpenCyber exploitation toolkit. The container executes searchsploit 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_exploit_search"
  }
}

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

B3.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, so the risk profile is known. The description adds genuinely non-obvious behavior: the container invokes `searchsploit` directly with argv tokens and never uses shell parsing, and execution is scoped to the selected engagement namespace. That tells the agent how arguments are interpreted and that path context matters, which the annotations do not.

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 action, then the execution model, then the path convention. No filler, though the sentences are somewhat clipped and could bind the path note more explicitly to the `working_directory` parameter.

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?

An output schema exists, so return values need no explanation, and the argv/no-shell detail covers the riskiest invocation behavior. However, for a destructive, open-world tool with four undocumented parameters, the definition omits argument format examples, timeout or output-size expectations, and how `engagement_id` affects execution scope.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden, and it only partly does: it clarifies that `arguments` is a token array passed without shell parsing and that relative paths should be used for engagement artifacts (implying `working_directory`). It says nothing about `engagement_id` scoping mechanics or the purpose of `stdin`, leaving half the parameters undocumented anywhere.

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 states a specific verb and resource: run an exploit search via `searchsploit` from the OpenCyber toolkit. That is concrete enough for an agent to know what happens, though it does not differentiate this tool from other recon/search siblings beyond naming the underlying binary.

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 choose this over alternatives or what preconditions apply, beyond an incidental note to use relative paths for engagement artifacts. An agent gets no when/when-not framing or routing hint.

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