Skip to main content
Glama

zerodom_add_identity

Register a second user identity or auth header for cross-tenant IDOR testing. Set it up from a Chrome profile endpoint, live tab cookies, or a storage_state file, then compare responses.

Instructions

Register a second identity (e.g. user B) for cross-tenant IDOR testing.

Source of the session (pick one):

  • endpoint — a SECOND real Chrome profile, already logged in as B, reached over its own relay: endpoint="ws://127.0.0.1:8766/cdp/local". Each request leaves through that profile's real Chrome (real fingerprint, its own live login) — no snapshot, no re-login, no blank browser. Set it up once: zerodom relay --port 8766, load the extension in profile B and click Connect (it auto-finds a free port — no URL to paste), log in. The port it lands on shows in that profile's popup; pass its /cdp/ endpoint here. Its active tab must be on the target origin (same-origin, like 'live'). Best for a WAF target where two real profiles beat cookie-swap.

  • from_live=True — snapshot the CURRENT logged-in tab's cookies. Log in as B, call this, then log the tab back into A. No file to manage.

  • storage_state — a Playwright storage_state JSON file (cookies + origins).

  • neither — anonymous (only useful with header for token auth).

header adds one extra request header ('Authorization: Bearer …'); call again to add more. The current logged-in session is always available as identity 'live' without registering.

via picks the transport:

  • "auto" (default) — if a browser is attached, send with the REAL Chrome fingerprint by swapping this identity's cookies into the live tab per request (passes a fingerprinting WAF like DataDome); else Playwright's HTTP client.

  • "live" — force the real-fingerprint swap path.

  • "http" — force Playwright's APIRequestContext (cookies yes, Chrome's TLS fingerprint no). For CI/headless, or a cross-origin URL the in-page fetch can't reach (no CORS).

Once two identities exist, zerodom_compare_identities(url) fetches the same URL as each and flags a byte-identical response — the cross-tenant IDOR tell.

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

Input Schema

NameRequiredDescriptionDefault
viaNoauto
nameYes
headerNo
endpointNo
from_liveNo
storage_stateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.5
    • addedInput schema / properties / endpoint
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Endpoint"
      +}
    • addedInput schema / properties / from_live
      Added value: +{
      +  "default": false,
      +  "title": "From Live",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / via
      Added value: +{
      +  "default": "auto",
      +  "title": "Via",
      +  "type": "string"
      +}
  2. Addedv0.0.9

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely meets it: it discloses that 'auto' may swap cookies into the live tab per request to pass fingerprinting WAFs, that 'http' loses Chrome's TLS fingerprint, that the existing logged-in session is always available as identity 'live', and that header can only be extended by calling again. It stops short of stating side effects (persistence across calls, whether re-registering a name overwrites, cleanup) and any error/auth-failure behavior.

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?

Front-loaded with the one-line purpose, then organized into labeled source options and a transport section — easy to scan. It is on the long side and the endpoint bullet drifts into CLI setup chatter ('it auto-finds a free port — no URL to paste') and mild redundancy ('no snapshot, no re-login, no blank browser'), but nearly every sentence carries decision-relevant information.

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

Completeness4/5

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

For a 6-parameter, configuration-heavy tool with no annotations, the description covers the source-selection matrix, transport implications, and the downstream compare step. An output schema exists so return values need not be explained. The missing pieces are lifecycle details — whether identities persist, whether re-registering a name replaces an existing one, and how to remove one — rather than anything needed to make a correct first call.

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

Parameters5/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, and it does: it explains the semantics of endpoint (format shown via a concrete ws:// URL, its prerequisite tab origin), from_live (snapshots the current tab's cookies), storage_state (Playwright JSON of cookies+origins), header (single extra header, additive on repeat calls), and each via value. Only the required `name` parameter is left implicit, which is the one self-evident case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Register a second identity' — plus the motivating scenario (cross-tenant IDOR testing). It also positions itself against the sibling that consumes its output by naming zerodom_compare_identities(url) as the follow-up step, so an agent can place it in a workflow without opening other schemas.

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

Usage Guidelines5/5

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

Explicitly enumerates the four mutually exclusive sources of a session (endpoint, from_live, storage_state, none) and gives the condition that selects each, including 'neither — anonymous (only useful with header for token auth)'. It also states when a real Chrome profile beats cookie-swap ('Best for a WAF target') and when to force 'http' (CI/headless, cross-origin/no CORS), which is exactly the when-not guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.