clawsmith.com/signal/vault-policy-filtered-listing
โ IssueUnderserveddev_tool_cliLive
HashiCorp Vault LIST returns all paths regardless of caller policy with no filtering
vault list on a KV mount returns every path even if the calling token has no read/write permission on most of them. Operators cannot scope the list output to paths the user can actually access. The issue has been open since 2018 with 106 reactions. vkv (a third-party tool with 109 stars) does recursive listing but does NOT read Vault policies to filter results; it still shows all paths. No tool exists that reads a token's effective policies and renders only the paths the caller can legitimately operate on.
Score Breakdown
GitHub
165
Social Proof 1 sources
Gap Assessment
UnderservedExisting solutions leave gaps
8-year-old open issue; vkv solves recursive traversal only, not policy-aware filtering; gap for a CLI that computes effective accessible paths from Vault policy APIs and renders a filtered explorer
Virality Score
165
across 0 platforms
Details
Signalissue
Ecosystemdev_tool_cli
Sources1
Platforms0
Updatedunknown
Trendโ stable
Top ideas
All ideas โ