Content filtering
Checking what goes into a model and what comes out of it against content rules, and stopping or flagging a request that fails them. Distinct from data maskingData maskingReplacing the personal or confidential values in a prompt with placeholders before it leaves for a model, and putting them back in the answer. Anonymisation, where the values are gone for good, and pseudonymisation, where they return, are the two forms; which fields count as sensitive is the application's question, not the module's.SAP only, which hides values: a filter refuses content.
Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP
Overview
No SAP artifact is confirmed here for Node.js.
A Node.js coverage assessment has not been written. View all flavors
No community artifact is confirmed here for Node.js.
A Node.js coverage assessment has not been written. View all flavors
Artifacts
Seen working
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Details
Coverage
For your agent
- Ref
capability:content-filtering- JSON
- /capabilities/content-filtering.json
- MCP
- Connecting an agent