TeleKey parity: checking… Telescript GitHub ↗ arXiv ↗ 100%

Scoped access for MCP agents.

MODELED AFTER TELESCRIPT'S PERMIT · 1995 TELEKEY CONTROL SYSTEM SYSTEM DIAGRAM AGENT TELEKEY MCP SERVER / TOOLS SUB-AGENT REQUEST / CALL AUTHORIZED — PASSES UNAUTHORIZED — BLOCKED SCOPED KEY — NARROWED RESULT RETURNS — BYPASSES TELEKEY 1 2 3 4 5 6 7 8 9 LEGEND 1 · AGENT 2 · REQUEST / CALL (OUTBOUND) 3 · TELEKEY GATE (KEYED CONTROL POINT) 4 · AUTHORIZED — PASSES 5 · UNAUTHORIZED — BLOCKED 6 · MCP SERVER / TOOLS 7 · RESULT RETURNS (BYPASSES TELEKEY) 8 · SUB-AGENT (SCOPED IDENTITY) 9 · SCOPED KEY — NARROWED

Your agent connects to MCP servers — and everything it does stays inside the permissions you granted.

So when something goes wrong — a bad instruction, a compromised tool, a prompt injection — the damage is already bounded.

Works with Claude Code, Codex, and any MCP agent, via a PreToolUse hook.

Watch an unauthorized tool call get stopped

Without TeleKey — the usual setup today

The agent holds your credentials directly. Nothing evaluates what it asks for.

The scoped key

what TeleKey handed the sub-agent

TeleKey OFF

Outbound calls

what the agent actually got to do

With TeleKey — the same attack, scoped

Same request, same injection. Every call now goes through the engine first.

The scoped key

what TeleKey handed the sub-agent

The TeleKey engine

checks every call before it runs

Outbound calls

what the agent actually got to do

Every line below came from a real call

Requested capabilityVerdictWhy

Put it in front of your own agent

This repo is a plugin marketplace. Point Claude Code at it — no clone, no build.

/plugin marketplace add stefans71/telekey-mcp
View source on GitHub →

Scope & honesty

Enforcement bounds what a hijacked agent can do; it does not stop the hijack. Signing here is HMAC-SHA256 via Web Crypto — a stand-in for RFC 9068 JWTs, exactly as in the Node reference.