MCP Integration

Fail

Audited by Runlayer on Feb 26, 2026

Risk Level: HIGH
Scan Summary
Max Score
91%
Files
7
Flagged
3
Chunks
11
Flagged Files (3)
mcp-integration/references/authentication.mdHIGH
91.3%

Malicious tool definition detected

**Not directly supported in MCP configuration.** **Workaround:** Wrap in stdio server that handles mTLS: ```json { "secure-api": { "command": "${CLAUDE_PLUGIN_ROOT}/servers/mtls-wrapper", "args": ["--cert", "${CLIENT_CERT}", "--key", "${CLIENT_KEY}"], "env": { "API_URL": "https://secure.example.com" } } } ``` ### JWT Tokens Generate JWT tokens dynamically with headers helper: ```bash #!/bin/bash # generate-jwt.sh # Generate JWT (using library or API call) JWT=$(generate-jwt-token) echo "{\"Autho

mcp-integration/references/server-types.mdLOW
69.0%

Tool passed security scan

mcp-integration/SKILL.mdLOW
66.0%

Tool passed security scan

Passed Files (4)Click to expand
mcp-integration/examples/stdio-server.jsonOK
45.0%

Tool passed security scan

mcp-integration/references/tool-usage.mdOK
38.2%

Tool passed security scan

mcp-integration/examples/http-server.jsonOK
16.4%

Tool passed security scan

mcp-integration/examples/sse-server.jsonOK
15.2%

Tool passed security scan

Audit Metadata
Max File Score
91%
Classification
KNOWN_SERVER_ALL_UNKNOWN
Files Scanned
7
Files Flagged
3
Chunks Analyzed
11
Analyzed
Feb 26, 2026, 04:59 PM
Security Audit — runlayer — MCP Integration