suggest_field_protection
Suggests per-field protection methods (hmac, mask, redact, drop, none) with a one-line reason from field names and types only, so you can review and choose protections before creating a pipeline.
Instructions
Suggest per-field protection (hmac, mask with an optional preserve, redact, drop, or none, each with a one-line reason) for a pipeline's source fields, computed by the configured CodeGen model from field NAMES and TYPES ONLY: no row value is sent to the model. Stateless: nothing is saved or changed. Pass pipeline (an existing pipeline name; its stored source schema is used) or fields (an array of {name, type}, e.g. the schema you are about to create). A field that already carries protect shows it as current next to the suggestion. Show the suggestions to the user and ask which to accept before passing any of them as the protect map to create_pipeline; never apply them on your own. With preset (delimited sources only) the server's rule-based preset classifier is used instead of the model: each field gets an identifier class, a method and a reason, and the result lists the fields it did not recognise and review notes; show all of it, including the review notes, to the user.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "suggest_field_protection"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fields | No | Fields to classify (use this OR pipeline): [{"name": ..., "type": ...}] | |
| preset | No | Optional preset to classify against instead of the model (delimited/CSV sources only). The result can be enforced on create_pipeline with protect_preset. | |
| pipeline | No | Existing pipeline name (use this OR fields) |