Policy-as-Code for Agent Credentials: Restricting Access Beyond Raw Keys
radim11 · reddit · 2026-08-19
Proposes adding a declarative "policy-as-code" layer around credentials passed to coding agents (e.g., GITHUBTOKEN), instead of granting the full permissions of the underlying credential.
The Logic:
- Granular Control: Define rules for allowed Hosts, Methods, and Paths (e.g., allow GET issues, but explicitly deny DELETE on production repos).
- Audit & Isolation: The agent never sees the raw credential; requests are validated and logged against the policy.
Seeking Feedback:
- Is "allow + explicit deny" clearer than "allow-only"?
- Are Host/Method/Path rules sufficient in practice?
- How to make this safe for PR review and workable across dev/staging/prod?
More from coding & agent
- Using Codex and NeMo-RL to Train Models on Slurm Clusters — JFPuget · 2026-08-19
- Consumer agents got so good that email and calendar apps look disruptable — omooretweets · 2026-08-19
- Stripe integrates with Grok Bot for agentic customer support operations — jeff_weinstein · 2026-08-19
- Multi-Agent Workflow: Splitting Tasks Beats One全能 Agent for Dev — RonnySaya · 2026-08-19
- Upcoming Agent course series: First video on evaluating evals — ben_burtenshaw · 2026-08-19
- Claude Code plugin rewrites output to plain English using local LLMs — tom_doerr · 2026-08-19