tool-allowlist
Skill0 starsChanged 7 months agoMITView on GitHub
1 other project uses a version of this.
Adopted by
Most recently taken up by
- frankxai/skillstheir own version, first seen Sep 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- frankxai/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audit-trailSkill
- authSkill
- fan-outSkill
- observabilitySkill
- rate-limitingSkill
- response-cachingSkill
- schema-validationSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Default-deny (allow mode) recommended for production
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Tool Allowlist
Capability
Per-tenant tool access control with wildcard pattern matching, version tracking, and allow/deny modes.
Package
@reaatech/mcp-gateway-allowlist — packages/allowlist/src/
Components
| Component | Purpose |
allowlist-manager.ts | Core evaluation: checkToolAccess, matchesPattern, validateAllowlist |
allowlist.middleware.ts | Express middleware for tool access control |
dynamic-allowlist.ts | Runtime allowlist updates with version tracking and rollback |
types.ts | AllowlistMode, ToolAllowlist, AllowlistCheckResult |
Allowlist Modes
| Mode | Behavior | Use Case |
allow | Only listed tools allowed (default deny) | High security environments |
deny | Listed tools blocked (default allow) | Permissive environments |
Pattern Syntax
| Pattern | Matches |
glean_* | Tools starting with glean_ |
*_search | Tools ending with _search |
* | All tools |
tool_a|tool_b | Exact tool names (pipe-separated) |
Error Handling
- 403 Forbidden — Tool access denied, JSON-RPC error format
- Error includes tool name, tenant, and policy mode
- Denied requests are never forwarded to upstreams
Security Considerations
- Default-deny (allow mode) recommended for production
- Patterns validated at config load time
- Version tracking enables rollback on bad updates
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.