Text inspector

Inspect one text: sensitivity, tier, injection, policy and action.

Inspect one text: sensitivity, tier, injection, policy and action.

This screen belongs to the Secure deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.

Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.

Step-by-step actions

  1. Text inspector → enter Hello as a clean sample.
  2. Select request/context and click Inspect (Инспектировать), or press Ctrl+Enter.
  3. Repeat with docs@example.invalid and a synthetic injection preset.
  4. Compare classes, final decision and request ID.
  5. Use a separate integration call through Secure to verify proxying.

Every control and its meaning

Control / parameterValues, units and effect
Текст для инспекции / TextA synthetic text or preset; inspection checks text without generating an LLM response.
Точка инспекции / Pointrequest/response/attachment/tool_input/tool_output/web_content. Attachments use the separate supported text contract.
Контекст приложения / ContextOptional dev/chat/subagent string; not a Tenant ID or access permission.
Результат / Resultclassification, classes, decision, policy, tier, confidence, latency and request ID explain the outcome.

Verify the result

An email class does not always mean mask: active policy defines the action. Check scope, point and final rule ID.

Errors, disabling and reverting changes

For timeout/503, the operator checks the inspector. Correct point/context/format for 422; Clear changes local input, not audit.

Secure inspector: actual allow response for harmless text
Secure inspector: actual allow response for harmless text
2026-10-15 · Actual staging; normal operator sign-in, synthetic PUBLIC text, pipeline response and request ID returned by the gateway. This inspector does not prove tenant-specific policy scope.
  1. Text to inspect
  2. Inspection point
  3. Application context
  4. Inspect

Detailed security settings · Traffic analysis · FAQ · All application sections