Capabilities

Capabilities

AHP-CAP-001 — MUST. A harness advertises only effects it can enforce for the current interception, and a backend returns only advertised effects. AHP-CAP-002 — MUST. Every hooks/intercept request contains capabilities.effects, and a Tool Interception harness includes deny there for tool.before.

Every hooks/intercept request MUST include capabilities.effects. A minimal Tool Interception advertisement for tool.before is:

{
  "capabilities": {
    "effects": ["deny"]
  }
}

A harness claiming the Tool Interception profile in this protocol revision MUST advertise deny in capabilities.effects for tool.before, declaring that it accepts and enforces a valid deny effect. A backend MUST return only effects advertised in that request. Returning an unadvertised effect is an operational protocol failure, not an implicit no-op. The harness MUST apply the interceptor’s configured failure policy. Capabilities describe the current event and runtime, not only the harness product. A backend MUST NOT infer capabilities from provider name, provider version, transport, or native payload. Additional effects and their option blocks are defined in capability bounds and are optional unless a claimed profile requires them. The current schema enumerates effect types; reverse-DNS extension metadata does not authorize an unknown effect type.