docs: add agent identity and per-tool authorization guide#453
Open
saneGuy wants to merge 1 commit into
Open
Conversation
|
|
Vendor-neutral guide for verifying agent identity and enforcing per-tool permissions in multi-agent deployments. Complements RAKs and the security policy template work in stripe#293.
saneGuy
force-pushed
the
docs/agent-identity-authorization
branch
from
fc3b871 to
1fca69d
Compare
Author
|
Friendly bump — all CI checks are passing. Happy to address any feedback if needed. |
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.
Summary
Adds a guide for verifying agent identity and enforcing per-tool permissions
when multiple agents or third-party tools connect to the Stripe MCP server.
Complements RAKs and the security policy template work in #293 by addressing
agent-level authorization: verifying which agent is acting, not just what
API key it holds.
Why
When multiple agents share Stripe API keys or third-party agent frameworks
connect to the MCP server, there is no standard way to verify which agent
placed a charge or created a refund. This guide describes a deployment
pattern for environments that need agent-level attribution and per-tool
permission enforcement.
Files
docs/AGENT-IDENTITY.md— new guide (vendor-neutral, pattern-based)README.md— one section linking to the guideNo code changes
Docs only.