Skip to main content
The lower-level primitive used by safetyCheck. You usually don’t need to call this directly — wrap your handler with safetyCheck instead. Use checkSafety when you want fine-grained control (e.g. checking content from outside an MCP tool path).

Parameters

string
required
The content to validate.

Returns

SafetyCheckResult

Behavior

  • POST https://api.sedata-ai.tech/security/safety-check
  • Body: { "content": "<your content>" }
  • Header: Content-Type: application/json
  • If setTelemetryApiKey(...) was called (typically by instrumentServer), also sends x-api-key: <key>.

Failure modes

The function never throws.

Example

Authentication

Set the key once at startup:
If you call instrumentServer(...) with exporterAuth, the key is set for you.

See also

safetyCheck

The high-level wrapper — what most users want.