tools / mcp audit / rules / secret in url · v0.1.0 · View source · Edit on GitHub
MCP audit rule · v0.1.0

Secret in URL

URLs end up in logs, history and shared configs, so a credential in one is easily exposed.

  • each server checks
  • 2 test fixtures

high secret-in-url

Flagged

  3       "s": {
  4 >       "url": "https://••••••@example.com/mcp"
  5       }

Fix

Remove credentials from the URL and send them in a header referenced from an input or env variable, then rotate the exposed key.

Fine

{
  "mcpServers": {
    "s": {
      "url": "https://example.com/mcp"
    }
  }
}

References

← All rules

Running agents in production?Qlucent assesses agent permissions and data boundaries. →