Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_browser_network_rules

Destructive

Configure browser request interception by blocking URL patterns, replacing URLs, and adding extra headers to control network traffic during authorized engagements.

Instructions

Configure browser request interception with blocked URL patterns, URL replacements, and extra request headers.

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>"
    },
    "name": "oc_browser_network_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
engagement_idYes
extra_headersNo
blocked_patternsNo
url_replacementsNo

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 this as destructive, non-read-only, non-idempotent, and closed-world. The description adds that the tool configures browser request interception rules, which gives useful domain context beyond the annotations, but it does not explain whether rules replace or append, how active sessions are affected, or whether changes are reversible.

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?

The description is a single efficient sentence with the core purpose front-loaded and no unnecessary wording. It is appropriately sized, though its brevity contributes to gaps in usage and parameter explanation.

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?

The tool is a destructive browser mutation with five parameters and no schema descriptions. Although annotations and an output schema reduce some burden, the description still omits required parameter meaning, rule semantics, and behavioral consequences of applying interception rules.

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 must compensate for parameter meaning. It names blocked_patterns, url_replacements, and extra_headers in natural language, but gives no format or syntax details and does not mention the required engagement_id or session_id parameters.

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: "Configure browser request interception" along with blocked patterns, URL replacements, and extra headers. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as oc_browser_network_log.

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 explicit guidance on when to use this tool, when not to use it, or which alternatives to choose. The purpose implies a configuration scenario, but the agent must infer the usage context without any exclusions or routing guidance.

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