← All 12 review guides

TokenIsolate

Local synthetic PASS Local execution evidence only

Supported boundary

Local sensitive-text patterns, redaction, token operations and route/flow checks; no network proxy configuration or exhaustive privacy guarantee.

10 actual local calls cover 10 advertised operations. These results do not establish marketplace approval, a completed formal host self-test, or production OAuth readiness.

Reproduce the synthetic workflow

Use prerequisite operations in listed order, the current discovered schema and newly returned IDs. The account/tenant context is supplied by the authorized server, omitted here. Local result IDs are examples from one isolated run. These records are not production data or a production-host test.

Download synthetic inputs, expected fields and actual local results

Five positive review prompts

1. Using the supplied synthetic fixture inputs, register a local sensitive-data route rule; then record sensitive-data exposure across supplied stages. Explain the returned evidence and limits.

Expected tools: tokenisle_registerRule, tokenisle_auditFlow

tokenisle_registerRule: denied email rule; tokenisle_auditFlow: EXPOSED with one finding

Formal host testing is tracked separately; this page documents local execution only.

2. Using the supplied synthetic fixture inputs, list registered sensitive-data route rules; then recover an original value from a local token. Explain the returned evidence and limits.

Expected tools: tokenisle_listRules, tokenisle_deisolate

tokenisle_listRules: one rule; tokenisle_deisolate: recover synthetic original

Formal host testing is tracked separately; this page documents local execution only.

3. Using the supplied synthetic fixture inputs, detect sensitive-data patterns in supplied text; then compare a candidate value with a recovery token. Explain the returned evidence and limits.

Expected tools: tokenisle_scan, tokenisle_validate

tokenisle_scan: one synthetic email; tokenisle_validate: matching candidate ok

Formal host testing is tracked separately; this page documents local execution only.

4. Using the supplied synthetic fixture inputs, replace sensitive text with local recovery tokens; then suggest a category for unclassified sensitive text. Explain the returned evidence and limits.

Expected tools: tokenisle_redact, tokenisle_classifyUnknown

tokenisle_redact: one token; no original in redacted text; tokenisle_classifyUnknown: local stub note and nullable suggested

Formal host testing is tracked separately; this page documents local execution only.

5. Using the supplied synthetic fixture inputs, evaluate a sensitive-text routing decision; then summarize local sensitive-data isolation state. Explain the returned evidence and limits.

Expected tools: tokenisle_enforceRoute, tokenisle_snapshot

tokenisle_enforceRoute: DENY with autoRedact; tokenisle_snapshot: one vaulted value and one audited event

Formal host testing is tracked separately; this page documents local execution only.

Three unsupported requests

Explain the limitation without invoking domain tools to simulate the requested external action or claiming completion. Actual host no-tool behavior is not established by these local fixtures.

Evidence limits

All data here is synthetic and comes from isolated local executions. No passwords, account identifiers or private reviewer instructions are supplied. A verified demonstration recording, actual host conversations and saved submission checks remain separate work.

공통 요금표 · 네 마켓 동일 USD 요금