mcp-risk-review skillA
mcp-risk-review is agent-read markdown (skill) from yeaight7/agent-powerups: Use when an MCP server is about to be enabled, added to agent config, or upgraded -- a staged server config is a candidate for activation, a third-party server is proposed from a registry, or an existing entry changes transport, credentials, or tool surface..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## Purpose Triage the risk of an MCP server before it gains access to the session. An enabled server's tools execute with real filesystem, network, and credential reach; the review happens before enablement, not after the first incident. ## When to Use - A staged MCP server config is a candidate for enabling - A third-party MCP server is proposed from outside the repo - An existing server entry changes transport, credentials, or tool surface - A long-enabled server is due a periodic re-review For filesystem-server path boundaries in depth, continue with the filesystem-mcp-guardrails skill after this triage. ## Inputs - The server config entry: command, args, env, transport - The server's declared tool list (from its manifest or a smoke run) - What the session can reach if the server misbehaves ## Workflow 1. **Launch vector.** Pinned, locally installed binaries beat remote latest-version execution: ```sh rg -n 'npx -y|@latest|curl .*\| *sh' <config-file> ``` Unpinned remote execution is a P1 by default — the server reviewed today is not necessarily the server that runs tomorrow. …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/mcp-risk-review@git:20260606.835b58amdr add yeaight7/agent-powerups/mcp-risk-review@sha256:664e6db810019c93Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_e3fn6f6llflem5ba)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.835b58a latest | 2026-06-06 | 835b58a | 3,520 B | A | view · diff |
| git:20260504.824f64a | 2026-05-04 | 824f64a | 68 B | B | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3520 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e3fn6f6llflem5ba GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/mcp-risk-review GET https://markdownregistry.com/api/v1/blob/664e6db810019c936eaf5fbf0b8e0e85bd9d5186a92588555cd3b021c69e19b3
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.