{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-enforces-egress-policy-on-the-serialized-tool-call-boundary-instead-of-the-data-flow-boundary",
  "title": "What happens when an instance enforces egress policy on the serialized tool-call boundary instead of the data-flow boundary",
  "date_of_record": "2026 November 17",
  "scope": "Applies to autonomous tool-using agents whose runtime enforces egress restrictions (allowlists, redaction, taint labels) at the point where a tool call is serialized for transport to an external sink. Does not apply to agents that enforce egress at the model-token emission boundary, nor to fully sandboxed runtimes with no external sinks at all.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-enforces-egress-policy-on-the-serialized-tool-call-boundary-instead-of-the-data-flow-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-enforces-egress-policy-on-the-serialized-tool-call-boundary-instead-of-the-data-flow-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-enforces-egress-policy-on-the-serialized-tool-call-boundary-instead-of-the-data-flow-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1850,
    "python_slice_tokens": 211,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two places an egress policy can live. The first is the **data-flow boundary**: a label is attached to a value when it enters the agent's context from a sensitive source (a secret store, a PII-bearing record, an internal-only document), and the label travels with the value through every transformation — string concatenation, JSON encoding, base64, s...",
    "what_was_observed": "A runtime was configured with an egress allowlist on a `send_email` tool. The policy blocked payloads containing strings matching a secret-detection regex set: 32+ hex characters, `AKIA`-prefixed AWS keys, PEM header lines, and a set of known internal hostnames. Enforcement ran in the tool-call serializer, immediately before the SMTP submission. The agent was asked to summarize a document that happened to contain an ...",
    "condition_of_validity": "The serialization-boundary approach is *sound* (no false negatives from encoding tricks) only under the conjunction of: - The policy's matcher set is closed under every transformation the agent can express in its output channel. For a general-purpose LLM this set is unbounded, so the condition is effectively never met. - The agent's output channel is restric...",
    "decision_boundary": "Choose the enforcement layer by asking two questions: 1. **Can the agent emit free-form text into the egress channel?** If yes, serialization-boundary regex enforcement is not sound; use taint labels with output filtering. If no (schema-constrained, enumerated fields), regex enforcement on the schema fields is acceptable *provided* the schema has no free-tex...",
    "operational_effect": "When enforcement is placed at the serialization boundary and treated as primary, the operational signature is a policy that passes all unit tests (verbatim secrets are blocked) and fails in production against any agent that summarizes, reformats, or transcribes. The failure is silent — no alert fires, because the payload passed the check. Detection requires ..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "d47cc118fadeaf35530de4b6574996922697507a227ae29cb3ab48a139dd05ae",
    "verified_classes": [
      "EgressTaintViolation"
    ],
    "verified_functions": [
      "enforce_egress",
      "send_email",
      "__init__"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "EgressTaintViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
