Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_poc_lint

Read-onlyIdempotent

Statically reviews a PoC spec and code for engagement scope, allowed techniques, hard caps, and forbidden destructive patterns; returns blocking findings, warnings, and per-host scope verdicts.

Instructions

Static review of a PoC spec and its code: engagement scope for every host, supported technique class, hard request/time/output caps, and forbidden destructive or weaponized patterns. Returns blocking findings, warnings, and per-host scope verdicts. Signed-authorization coverage is enforced at run time, not here. Best-effort defense in depth, not a sandbox.

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

Input Schema

NameRequiredDescriptionDefault
spec_idYes
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real value on top: it discloses return shape (blocking findings, warnings, per-host scope verdicts), the enforcement boundary for signed authorization, and a candid limitation ("best-effort defense in depth, not a sandbox"). That caveat is exactly the kind of expectation-setting an agent needs before trusting a clean result; slightly short of 5 only because it says nothing about failure/lint-error modes.

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?

Four tight sentences, front-loaded with the operation and followed by outputs, boundaries, and the caveat in descending order of importance. No filler or restatement of the name.

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, return values need no explanation here, and the description covers checks, outputs, authorization boundaries, and guarantees. The single remaining hole is parameter meaning, which neither the schema (0% coverage) nor the description supplies.

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?

Two required parameters with 0% schema description coverage, and the description never explains what spec_id or engagement_id identify, their format, or how they relate to the engagement scope it checks. The prose hints that an engagement carries scope and a spec is the reviewed object, but that is inference, not documented semantics.

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 ("Static review of a PoC spec and its code") and enumerates exactly what is checked: host scope, technique class, caps, forbidden destructive patterns. "Static review" and "at run time, not here" cleanly separate it from execution-oriented siblings such as oc_poc_run without needing to name them.

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

Usage Guidelines4/5

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

Gives clear context that this is a pre-run, static check and explicitly bounds what it does not cover ("Signed-authorization coverage is enforced at run time, not here"). It stops short of stating a workflow (e.g., call before oc_poc_run) or explicit exclusions beyond that boundary note, so it is clear context rather than full when/when-not 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