Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_browser_set_state

Destructive

Inject cookies, localStorage, and sessionStorage into an active browser session to reproduce authenticated or preconfigured application states during authorized security testing.

Instructions

Set cookies, localStorage, and sessionStorage in a live browser session.

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_set_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
cookiesNo
session_idYes
engagement_idYes
local_storageNo
session_storageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the description is not the sole carrier of the safety profile. However, it adds almost nothing beyond them: it never says that existing cookies/storage are overwritten or merged, whether unset keys are cleared, or what happens if the session is not live - the key behavioral questions for a destructive mutation.

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 front-loaded sentence with no filler - it leads with the action and enumerates the affected resources. It is efficient but bordered on under-specified rather than padded.

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?

An output schema exists so return values need no explanation, but for a destructive, non-idempotent mutation with 5 undocumented parameters and no merge/overwrite semantics, the description is too thin to call safely. An agent cannot tell what state gets replaced or what prerequisites exist.

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 5 parameters, so the description must compensate and only partially does: it names the three state categories, mapping loosely to cookies/local_storage/session_storage. It says nothing about the expected shape of cookie objects or the required engagement_id/session_id, leaving the highest-risk parameters undocumented.

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 ('Set') plus the three resource types (cookies, localStorage, sessionStorage) and the context ('live browser session'), which distinguishes it from the read-side oc_browser_state sibling. It stops short of naming that sibling explicitly, so the differentiation is implied rather than stated.

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: nothing says a session must already exist, when to prefer injecting state over navigating/logging in, or how this relates to oc_browser_state. The only signal is the name and the phrase 'live browser session', so the agent must infer applicability.

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