What's Allowed
NPM · WHATS-ALLOWED-MCP · SCANNED AUG 3
Merged agent permission rules: which settings file wins, and which rules your client ignores.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 460 tokens (~115/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · whats-allowed-mcp
claude mcp add stcmain-whats-allowed-mcp -- npx -y whats-allowed-mcp
codex mcp add stcmain-whats-allowed-mcp -- npx -y whats-allowed-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stcmain-whats-allowed-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"whats-allowed-mcp"
],
"enabled": true
}
}
} openclaw mcp add stcmain-whats-allowed-mcp --command npx --arg -y --arg whats-allowed-mcp
mcp_servers:
stcmain-whats-allowed-mcp:
command: "npx"
args: ["-y", "whats-allowed-mcp"] {
"mcpServers": {
"stcmain-whats-allowed-mcp": {
"command": "npx",
"args": [
"-y",
"whats-allowed-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +61
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: excellent functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- Licence: MIT functional
- 1 Aug 26 5
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
permission_sources Which files decide, in what order ~105
Every settings file that can contribute permission rules, in documented precedence order, with whether it exists, whether it parsed, how many rules it carries, and what a leading `/` in its path rules anchors to. Use when a rule is not taking effect, when you cannot tell which file granted something, or to confirm a managed policy is or is not present.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | — | Absolute path to the project directory whose permissions you want. Defaults to the server's working directory. |
No output schema declared.
No examples provided.
rule_findings Rules that do not do what they look like ~132
Permission rules whose documented behaviour differs from their apparent intent: rules Claude Code accepts and never consults, `/path` rules in user settings that anchor at the config directory rather than your project, wildcards without a word boundary, allow rules on commands that run other commands, and allow rules a deny or ask rule reaches first. Each finding cites the documented behaviour. Use before trusting a guard rail you wrote a while ago.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | — | Absolute path to the project directory whose permissions you want. Defaults to the server's working directory. |
| kind | string | — | Restrict to one category of finding. |
No output schema declared.
No examples provided.
unattended_surface What proceeds with nobody watching ~109
The parts of the configuration that let a tool call go through without a human: the winning defaultMode, blanket allow rules, extra directories granted, whether bypass and auto modes are disabled, and hook commands — which run on agent events without a permission prompt of their own. Use before leaving an agent running unattended, or when reviewing what a repo's settings would do on your machine.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | — | Absolute path to the project directory whose permissions you want. Defaults to the server's working directory. |
No output schema declared.
No examples provided.
whats_allowed What this agent can do without asking ~114
Start here. One-call summary of the permission configuration in force for a directory: which settings files contribute, how many allow/ask/deny rules each carries, the winning defaultMode, blanket allows, hooks wired to tool use, and how many rules do not do what they look like they do. Use at session start, before an unattended run, or when a prompt appeared that you did not expect.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | — | Absolute path to the project directory whose permissions you want. Defaults to the server's working directory. |
No output schema declared.
No examples provided.