Policy demo
Auth brokering with a credentials file

Agents use whatever credentials they find in a project, and those are often a developer’s personal tokens. Qpoint’s auth broker replaces that token on each request with a scoped credential that you define once per service, and a policy keeps the agent from reading the credential itself. In the demo, Claude Code lists pull requests using a read-only token it never sees, and its attempt to post a comment fails because that token can’t write.
Gaurav Mahajan
Gaurav Mahajan
November 18, 2026

About this demo

In this demo, Qpoint’s auth broker replaces the token on Claude Code’s requests to GitHub with a read-only token created for agents. The setup has two parts: the auth broker plugin and a credentials file with one record for api.github.com. Keeping credentials in a file is a common pattern. In Kubernetes, for example, secrets are mounted into the pod as a file in the same way.

We ask Claude to take the GitHub token from the project’s .env file and list open pull requests with curl. The audit log shows Claude reading the .env file, running the curl command, and sending the request to GitHub. Qpoint replaced the personal token on that request with the scoped one. When Claude then tries to post a comment on a pull request, GitHub returns a 403, because the token GitHub received is read-only.

The credentials file is on the same machine as the agent, so we add a policy that denies any read of credentials.yml. Without restarting anything, we ask Claude to read the file, and Qpoint denies the read. The agent can work with the credential, but it can’t see it.

See Qpoint in action in your environment
Request access and we'll get you set up.
Request Access