stcmain/whats-allowed-mcp

Shows what your coding agent can do without asking you. Reads every settings file that contributes permission rules — managed policy, project, git-ignored local, user — and reports the merged result with provenance: which file each rule came from, which `defaultMode` wins, what proceeds unattended (blanket allows, additional directories, hook commands), and which rules the client accepts and then ignores (path rules on `Write`/`Glob`, `param:value` rules on a tool's primary content field, unanchored allow globs, `/path` rules in user settings that anchor at the config directory instead of your project, allow rules a deny or ask rule reaches first). Each finding links to the documented behaviour it comes from; there is no risk score and no simulated verdict for a hypothetical command. Four read-only tools; no child processes, no network, no writes, and `env` entries are read by name only. Install: `npx -y whats-allowed-mcp`. Registry id `io.github.stcmain/whats-allowed-mcp`. MIT.

Project

Browse this MCP server in the TensorBlock MCP Index.