Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_ip

Destructive

Inspect and configure network interfaces, addresses, routes, and SocketCAN links to bring can0 up or set wireless interfaces to monitor mode without switching to a shell.

Instructions

Inspect and configure network interfaces, addresses, routes, and SocketCAN links. Use this to bring can0 up or put a wireless interface into monitor mode without dropping into oc_bash. 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_ip"
  }
}

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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the write/destructive profile is covered. The description adds genuinely new context: it executes inside the selected engagement namespace and expects relative paths for engagement artifacts. It says nothing about privilege requirements or what happens to an existing interface configuration when arguments are applied.

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?

Two sentences, front-loaded with capability scope and followed by concrete usage examples. Nearly every clause earns its place, though the oc_bash comparison is slightly redundant with the sibling guidance an agent already has.

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 not be described. However, for a pass-through CLI wrapper whose behavior depends entirely on free-form 'arguments', the definition gives illustrative examples but no sense of the accepted argument grammar or scope of what can be changed, leaving meaningful gaps.

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% across four parameters, so the description must carry the load and largely does not. 'Arguments' — the most important parameter, clearly a raw argument vector passed to the underlying CLI — is never explained, and stdin is unaddressed. Only engagement_id and working_directory are obliquely touched by the namespace/relative-path sentence.

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 pair ('inspect and configure') over a specific resource set: network interfaces, addresses, routes, and SocketCAN links. This clearly distinguishes it from the general-purpose oc_bash sibling, though it never states plainly that it wraps the `ip` command, which is the real identity of the tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use examples ('bring can0 up', 'put a wireless interface into monitor mode') and names the alternative it avoids (dropping into oc_bash). No explicit when-not-to-use or preference rules versus oc_airmon for monitor mode, which is a plausible sibling overlap.

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