Prompt Security provides advanced protection for your AI applications against various security threats including prompt injections and sensitive data exposure, helping ensure safe interactions with LLMs. To get started with Prompt Security, visit their website:Documentation Index
Fetch the complete documentation index at: https://docs.portkey.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
Get Started with Prompt Security
Using Prompt Security with Portkey
1. Add Prompt Security Credentials to Portkey
- Click on the
Admin Settingsbutton on Sidebar - Navigate to
Pluginstab under Organisation Settings - Click on the edit button for the Prompt Security integration
- Add your Prompt Security API Key and API Domain (obtain these from your Prompt Security account)
2. Add Prompt Security’s Guardrail Check
- Navigate to the
Guardrailspage and click theCreatebutton - Search for either “Prompt Security Prompt” or “Prompt Security Response” depending on your needs and click
Add - (Optional) Configure the check parameters (Backend
v1.16.0+):- Policy (
policy, object) — Prompt Security policy JSON used to configure individual detectors (e.g. Prompt Injection Engine, Sensitive Data, Secrets, Harmful Content Moderator, Topics Detector, Language Detector, Regex, Code Detector, URLs Detector, Sentiment, Token Limitation, Token Rate Limit, Unicode Detector, Data Privacy Guidelines, Natural Language Guardrails). The Response check supports a subset focused on output (e.g. Prompt Leak Detector). - Enable Redaction (
redact, boolean, defaultfalse) — Apply text modifications returned by detectors (e.g. PII sanitization, secret redaction, regex redaction) to the request/response. - Monitor Only (
monitorOnly, boolean, defaultfalse) — Run detectors and log findings without blocking the request/response. - User (
user, string) — User identifier for identity-aware policies and per-user token rate limiting. - User Groups (
userGroups, array) — User group memberships for group-based policy enforcement.
- Policy (
- Set any
actionsyou want on your check, and create the Guardrail!
Guardrail Actions allow you to orchestrate your guardrails logic. You can learn more about them here
| Check Name | Description | Parameters | Supported Hooks |
|---|---|---|---|
| Prompt Security Prompt | Protect a user prompt before it is sent to the LLM. Supports configurable per-detector policy. | policy (object), redact (boolean), monitorOnly (boolean), user (string), userGroups (array) | beforeRequestHook |
| Prompt Security Response | Protect an LLM response before it is sent to the user. Supports configurable per-detector policy. | policy (object), redact (boolean), monitorOnly (boolean), user (string), userGroups (array) | afterRequestHook |
3. Add Guardrail ID to a Config and Make Your Request
- When you save a Guardrail, you’ll get an associated Guardrail ID - add this ID to the
before_request_hooksorafter_request_hooksparams in your Portkey Config - Create these Configs in Portkey UI, save them, and get an associated Config ID to attach to your requests. More here.
- NodeJS
- Python
- OpenAI NodeJS
- OpenAI Python
- cURL

