Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_browser_navigate

Destructive

Navigate a live browser session to a URL and return status, headers, resolved URL, and page title. Use it to load pages and confirm reachability during authorized security testing.

Instructions

Navigate a live OpenCyber browser session to a URL and return the resulting status, headers, URL, and title.

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>",
      "session_id": "<session_id>",
      "url": "<url>"
    },
    "name": "oc_browser_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
session_idYes
timeout_msNo
wait_untilNoload
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/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 risk profile is covered by structured data. The description adds only that the operation acts on a live session and returns status/headers/url/title, which the output schema largely covers, and never explains that navigation may trigger page side effects or script execution.

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?

A single well-formed sentence with the action front-loaded and no filler. It is efficiently written, though its brevity contributes to the missing parameter and usage detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, open-world, potentially destructive browser tool with zero schema descriptions, the definition is under-specified: no wait/timeout semantics, no session or engagement context, and no guidance on when to refresh state afterward. The existence of an output schema excuses it from explaining return values, but not from the parameter 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 five parameters, so the description must carry the burden and does not. It mentions only 'URL' and is silent on engagement_id, session_id, timeout_ms, and wait_until, including the meaning of the 'load' default or the accepted values for that enum-less string.

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 ('Navigate a live OpenCyber browser session to a URL') plus the resulting outputs, which is far more informative than the bare name. It doesn't explicitly differentiate itself from siblings like oc_browser_action or oc_browser_get, 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?

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named. The phrase 'a live OpenCyber browser session' weakly implies that a session must already exist (matching the required session_id), but the agent must infer prerequisites and the choice between this and oc_browser_action.

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