Add Clay Seal to Tools & Frameworks#30
Open
pberlizov wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding Clay Seal (MIT, published on PyPI and npm this week, active).
It gives an agent an attested identity and a capability token that says which tools it may call, then authorizes each MCP tool call against that token. The credential is sender-constrained, so a token copied from a log is useless without the workload key it is bound to, and an agent can narrow its token for a single task before delegating. Fits alongside Clawvisor and PIC Standard in Tools & Frameworks. Directly related to agent/tool security and vendor-agnostic (SPIFFE, real GCP/Kubernetes/AWS node attestation).