auditing-mcp-tool-integrations SKILL.md skillA
auditing-mcp-tool-integrations from unboundcompute/security-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add unboundcompute/security-agent-skills/auditing-mcp-tool-integrations@git:20260816.4aab195Pins git:20260816.4aab195 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- unboundcompute/security-agent-skills
- Path
skills/auditing-mcp-tool-integrations/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260816.4aab195, committed Aug 16, 2026
- Size
- 6,710 bytes
- Repository stars
- 26
- License
- MIT
Red-team the tool layer of an AI agent: the tool definitions, metadata, and outputs that a model reads and trusts. Covers tool poisoning (instructions hidden in a tool's description), tool shadowing and name collisions, rug-pulls (definitions that change after approval), line jumping (metadata acting before any call), token and credential passthrough, and tool-output injection. Use when adding or reviewing a tool, an MCP server, or a tool-marketplace entry, or when auditing an agent's tool…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Auditing MCP tool integrations: the tool layer is attack surface When a model is given tools (over the Model Context Protocol or any equivalent tool interface), it does not just call them, it *reads* them: names, descriptions, parameter schemas, and returned data all enter the model context and are trusted by default. That makes the tool layer an injection surface distinct from user content, and one most reviews skip because they read tools as documentation instead of as model input. ## When to use - You are adding or reviewing a tool, an MCP server, or a marketplace/registry entry, especially a third-party one. - You are auditing an agent's full tool manifest and its trust assumptions. - You are deciding whether a tool needs pinning, sandboxing, or human approval. ## Scope check Audit tools and servers you own or are authorized to test. Do not tamper with tools others depend on. If you can't name the authorization, stop. ## The loop 1. **Read every tool definition as the model sees it.** Pull the exact names, descriptions, parameter schemas, and any metadata surfaced to the model. This text is model input, not docs. Anything imperative in it is a potential …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/auditing-mcp-tool-integrations@sha256:87cb04c039311f82The line at the top of this page pins the label git:20260816.4aab195, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mjbdum5jtud4qlmr)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 16, 2026.
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 (6710 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
unboundcompute/security-agent-skills · 26 stars · license MIT · pushed 2026-09-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mjbdum5jtud4qlmr GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/auditing-mcp-tool-integrations GET https://markdownregistry.com/api/v1/blob/87cb04c039311f822067c0e1d5b76f92f0b567faf8439a029f143907f87e104a
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.