ALLOW_TOOLS/DENY_TOOLS for an MCP server: prefix globs, a curated preset, and error messages that name what exists
- trust mitigators mixed − 3
These factors total -3, not 0: the score is bounded to 0–100 after they are summed, so this one is floored at 0. The factors are left as they were applied rather than rewritten to make the column add up.
mixed
The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.
grade last moved 6d ago · see ecosystem CVEs →
No known CVEs for this server.
No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.
[](https://mcpobservatory.com/servers/github:ni-c/mcp-tool-allowlist/security) Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of ni-c.