JournalDAY 104 / TIKTOK

FIELD NOTE / TIKTOK

Ask MCP to cancel a job.

The short film, the complete written thought, and the evidence behind it.

Journal September 28, 2026 · TikTok target January 9, 2027
Open the approved MP4 ↗

The TikTok conversation link will follow its public release.

Ask MCP to cancel a job.

Day 104 - 2027-01-09 PT target - TikTok

Video caption

Ask MCP to cancel a job. Schema is not the allow list. MCP solves permissions is untested. Ship the boundary note. Narration uses Eric's authorized AI voice clone. #EricFieldNotes

Full written post / accessibility read

I open the tools plane docs and look for cancel job, continue from prior response, and collect artifacts. Those verbs belong to a job contract. If they are missing, MCP is doing its real job as tools and data, not as the whole stack.

Next I ask where allow and deny are decided. Host, gateway, policy. If someone points only at the MCP schema, the enforcement story is incomplete. That is the field test for a tools plane claim.

I keep a sticky that says untested on any sentence that claims MCP alone solves permissions. Evidence boundaries matter when security is asked to sign.

Write one paragraph in the architecture doc: MCP is tools and data; enforcement is host side; job lifecycle is elsewhere. That short note saves a long false review later.

Narration uses Eric's authorized AI voice clone.

#EricFieldNotes

Four-beat scene transcript

1. Ask MCP to cancel a job.

I open the tools plane docs and look for cancel job, continue from prior response, and collect artifacts. Those verbs belong to a job contract. If they are missing, MCP is doing its real job as tools and data, not as the whole stack.

Visual: If the answer is silence, you found the boundary.

2. Then ask who enforces.

Next I ask where allow and deny are decided. Host, gateway, policy. If someone points only at the MCP schema, the enforcement story is incomplete. That is the field test for a tools plane claim.

Visual: Schema is not the allow list.

3. Label synthesis honestly.

I keep a sticky that says untested on any sentence that claims MCP alone solves permissions. Evidence boundaries matter when security is asked to sign.

Visual: MCP solves permissions is untested.

4. Ship the boundary note.

Write one paragraph in the architecture doc: MCP is tools and data; enforcement is host side; job lifecycle is elsewhere. That short note saves a long false review later.

Visual: Tools plane, named and limited.

More notes from the work ↗