Skip to main content
Control and respond

Filter personal data out of tool results (the PII filter)

The PII filter keeps personal data out of what your AI tools read through StackJack. When it is on, a StackJack tool that only reads data answers blank instead of handing back a result that holds…

Written By Christopher Scaminaci

Last updated 13 days ago

The PII filter keeps personal data out of what your AI tools read through StackJack. When it is on, a StackJack tool that only reads data answers blank instead of handing back a result that holds personal data. The AI is told why, and it can still ask to see the data for one call. StackJack records each time it does.

At a glance

  • What it does: answers blank when a StackJack read tool would return personal data.
  • Plan: Business and above.
  • Who: an Administrator.
  • Where: AI Governance → Privacy and data → Security scanning.

Who can use it

The PII filter is available when all of these hold:

  • Your organization is on the Business plan or above. A blank result is a block, and blocks are enforced from Business.
  • Scan StackJack tool traffic is on, and the StackJack tool-call source collects at the scan level or higher (see Data-loss rules, findings and scanning StackJack tool traffic).
  • The region your organization runs in has scanning of StackJack tool traffic available.

The switch is on the Security scanning page, under StackJack tool traffic, and is called Filter personal data out of tool results (PII filter). Only an administrator can change it. When the filter cannot act, the switch is greyed out and says why: "Turn on Scan StackJack tool traffic first." or "Available on the Business plan and above."

There is nothing else to set up. The filter uses its own fixed checks, so the rules you edit, and the packs you turned on or off, do not change what it finds.

What it checks

The filter reads the text values of a tool's result. It looks for seven kinds of personal data:

  • email addresses
  • phone numbers
  • dates of birth
  • national ID numbers
  • tax ID numbers
  • bank account numbers
  • driver's license numbers

It does not read field names, and it does not look for names of people or places. A tool that answers with a download link is not checked: the filter reads the link, not the file behind it. A person you exclude from content collection is not protected by it, in the same way they are not protected by the other rules on this lane.

Which tools it covers

Only tools that read. The filter never blanks the result of a tool that changes something, because the next step it gives the AI ("call the same tool again") would repeat the change. It also leaves alone the StackJack platform tools, the automation builder's live tool test, and the one-time marker some connectors return to continue a long request.

What the AI is told

When the filter blanks a result, the AI tool receives a refusal and nothing else from the vendor. It names the kinds of data and how many matches there were, never the data itself.

The result held personal data

  • Response blank: PII filter hit. The tool's result contained personal data (), so StackJack withheld the whole result. Nothing was changed in the connected system.

The check could not finish, and your organization withholds a result it cannot check

  • Response blank: the PII filter could not finish checking this result, and your organization withholds a result it cannot check. Nothing was changed in the connected system.

Both messages carry the same next step:

  • If the task needs this data, call the same tool again with "piiSafe": false (it can sit beside the tool's other arguments, or on the stackjack_run_tool or stackjack_run_readonly_tool call). StackJack records every result shown this way for your organization's administrators. Otherwise narrow the request so the result leaves the personal data out.

A refusal like this is the filter doing its job. It is not a fault, and StackJack does not offer to open a support ticket for it.

Letting the AI see the data for one call

The AI can add "piiSafe": false to a call, and the result then comes back exactly as the vendor sent it: no marker, no wrapper. The argument is optional. When it is left out, the filter is on.

What StackJack records when the AI asks for the data and the filter would have blanked the result:

  • One finding on the Findings page, named stackjack.pii-safe.override. It shows how many matches there were and never the data.
  • One entry in the audit trail. It names the tool, the connector, the number of matches and the kinds of rule that matched. It names the signed-in person when there is one, and says "a connection" when an automation made the call. It never holds the data.

A call that sends "piiSafe": false when the result holds nothing to hide records nothing beyond the ordinary record of the call.

The audit entry is written even for a call made before your staff notice was recorded, because it records what the AI asked for, not what a person did. The finding follows the staff notice rule like every other finding.

An override does not raise an alert in this release. Look for the finding and the audit entry above.

When the check cannot finish

A result that is very large, a check that runs out of time, or a fault in the checks can stop the filter from finishing. What happens next follows the setting Refuse the call when the scan cannot finish on the same page:

  • Off (the default). The result goes through unchecked, and StackJack logs the miss.
  • On. The result is blanked with the second message above, and the AI can still ask to see it with "piiSafe": false. That override is recorded, with the reason the check could not finish.

If personal data was found before the check ran out of time, the result is blanked either way.

A note on size

The filter tells the AI about the piiSafe argument by adding it to each read-only connector tool in the list of tools your AI client loads. That is about 170 bytes per tool, and it is added only for an organization that turned the PII filter on. If your AI client uses the compact or minimal tool list, far fewer tools carry it.

For how tools take arguments, see How tools work. For what each error code means, see Tool errors and troubleshooting.