Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_authorization_get

Read-onlyIdempotent

Retrieve and verify an engagement's operator-signed PoC authorization record, including targets, validity window, allowed technique classes, and custom-code allowance. Read-only; missing records return status=required.

Instructions

Read and verify the engagement's operator-signed PoC authorization record: targets, validity window, allowed technique classes, and custom-code allowance. Read-only; this tool never creates or edits an authorization. A missing signed record is reported as status=required, not invented.

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

Input Schema

NameRequiredDescriptionDefault
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description goes beyond them by disclosing what is inspected and, importantly, the failure semantics — a missing signed record returns status=required rather than fabricating one — which is meaningful behavioral context an agent cannot get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences: the first front-loads what is read and the fields inspected, the second covers read-only scope and the missing-record behavior. No filler, no repetition of the tool name or title.

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?

With an output schema present, the description needn't explain return values, and it correctly focuses on scope and edge-case behavior. It is nearly complete for a one-parameter read tool; the only gap is the absence of any placement in the broader workflow or cross-reference to the tool that creates or grants an authorization.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter, engagement_id, with 0% schema description coverage, so the description must compensate and it does only indirectly by framing the record as belonging to 'the engagement'. The parameter name is self-explanatory enough that this is adequate, but it adds no format, source, or lookup guidance for the identifier.

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 — reading a signed PoC authorization record for an engagement — and enumerates exactly what is returned: targets, validity window, allowed technique classes, and custom-code allowance. It never names a sibling tool, so differentiation is achieved only implicitly through the distinctive 'authorization' subject matter.

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

Usage Guidelines3/5

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

Usage is implied by 'read and verify' plus the negative scoping sentence ('never creates or edits an authorization'), which tells the agent this cannot be used to grant or modify authorization. However, there is no explicit statement of when in a workflow it should be called or which tool handles the write/grant side, leaving the alternative path unstated.

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